Optimizing keepalive and other background traffic in a wireless network

ABSTRACT

Systems and methods of optimizing network transaction traffic originating at a mobile device are provided. The systems and methods includes identifying network transaction parameters corresponding to an application and utilizing the network transaction parameters to execute a network transaction in advance of an expected schedule or after a delay to optimize the network transaction traffic.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of PCT Patent ApplicationNo. PCT/US14/36669 filed on May 2, 2014 entitled “OPTIMIZING KEEPALIVEAND OTHER BACKGROUND TRAFFIC IN A WIRELESS NETWORK” which further claimspriority to and the benefit of U.S. Provisional Patent Application Ser.No. 61/833,838 titled “KEEPALIVE ALGORITHMS FOR SIGNALING OPTIMIZATIONIN A WIRELESS NETWORK FOR TRAFFIC UTILIZING PROPRIETARY ANDNON-PROPRIETARY PROTOCOLS” filed on Jun. 11, 2013 (Attorney Docket No.076443-8170.US00); U.S. Provisional Patent Application Ser. No.61/836,095 titled “ENGINEERING DELAY IN SENDING BACKGROUND REQUESTS FORSIGNALING OPTIMIZATION IN A WIRELESS NETWORK FOR TRAFFIC UTILIZINGPROPRIETARY AND NON-PROPRIETARY PROTOCOLS” filed on Jun. 17, 2013(Attorney Docket No. 076443-8170.US01); and U.S. Provisional PatentApplication Ser. No. 61/836039 titled “IDENTIFICATION AND REPORTING OFKEEP ALIVE MESSAGES AND OTHER NON-USER INTERACTIVE TRAFFIC IN A MOBILENETWORK” filed on Jun. 17, 2013 (Attorney Docket No. 076443-8173.US02).The entire content of the aforementioned applications are expresslyincorporated by reference herein.

BACKGROUND

Many applications on mobile devices utilize long-lived connections to beable to immediately receive incoming data from their servers in thenetwork. Examples of such “always-on” applications can include instantmessaging applications (e.g., SKYPE, VIBER), push email clients andVoice over Internet Protocol (IP) applications. In order to maintain along-lived connection, applications are designed to periodically sendheartbeat messages or keepalive messages (or simply keepalives or KAs)to their servers.

While the keepalive messages from these always-on applications allow theapplications to receive messages with less delay, this improvement inlatency has associated costs. These costs include consumption of asignificant amount of energy in mobile devices, additional signaling inthe mobile network and bandwidth consumption. For example, to be able tosend keepalive messages frequently, a mobile device needs to frequentlytransition its radio between a high powered state and an idle state orremain in a high powered state instead of the idle state for a longerperiod of time, resulting in fast draining of battery. These radiotransitions also cause additional signaling in the networks as radioresource control (RRC) messages need to be exchanged between the mobiledevice and base station to establish a radio link. Furthermore, eachkeepalive message can be as large as 20-60 bytes in size, and a largenumber of such keepalive messages from multiple apps can add up toconsume a substantial chunk of the network bandwidth.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A-1 is an example schematic diagram that depicts optimization ofkeepalives by categorizing a keepalive as safe or unsafe andtransmitting an unsafe keepalive from a mobile device at one end of aconnection to another end of the connection over a network.

FIG. 1A-2 is an example schematic diagram that depicts optimization ofkeepalive traffic by advancing a keepalive from its expected schedule.

FIG. 1A-3 is an example schematic diagram that depicts optimization ofkeepalive traffic by delaying a keepalive beyond the keepalive period.

FIG. 1A-4 is an example schematic diagram that depicts optimization ofbackground traffic by delaying repeatable background requests.

FIGS. 1A-5-1A-9 are example diagrams that depict keepalive learningalgorithms to generate a rule set for isolating safe keepalives fromunsafe keepalives and selectively blocking the safe keepalives.

FIG. 1B illustrates an example diagram of a system where a host serverfacilitates management of traffic including keepalive and otherbackground traffic, content caching, and/or resource conservationbetween mobile devices (e.g., wireless devices), an application serveror content provider, or other servers such as an ad server, promotionalcontent server, or an e-Coupon server in a wireless network (orbroadband network) for resource conservation.

FIG. 1C illustrates an example diagram of a proxy and cache systemdistributed between the host server and a mobile device whichfacilitates network traffic management between the mobile device, anapplication server or content provider, or other servers such as an adserver, promotional content server, or an e-Coupon server for resourceconservation and content caching.

FIG. 1D illustrates an example diagram of the logical architecture of adistributed proxy and cache system, including a log storage andprocessing service.

FIG. 1E illustrates an example diagram showing the architecture ofclient side components in a distributed proxy and cache system,including a keepalive optimizer.

FIG. 2A illustrates an example diagram depicting an example ofclient-side components in a distributed proxy and cache system and akeepalive optimizer.

FIG. 2B illustrates an example diagram depicting additional client-sidecomponents in the distributed proxy and cache system of FIG. 2A.

FIG. 2C illustrates an example diagram depicting additional componentsin the proprietary/non-standard protocol adaptation engine shown in theexample of FIG. 2A.

FIG. 3A illustrates an example diagram depicting an example ofcomponents including a keepalive blocker, a keepalive traffic scheduler,a background traffic scheduler and a keepalive optimization reportingagent in the keepalive optimizer of FIG. 2A.

FIG. 3B illustrates an example diagram depicting an example ofcomponents in the keepalive blocker of FIG. 3A.

FIG. 3C illustrates an example diagram depicting an example ofcomponents in the keepalive traffic scheduler of FIG. 3A.

FIG. 3D illustrates an example diagram depicting an example ofcomponents in the background traffic scheduler of FIG. 3A.

FIG. 4 illustrates a block diagram depicting an example of server-sidecomponents, in certain embodiments of a distributed proxy and cachesystem residing on a host server that manages traffic in a wirelessnetwork (or broadband network) for resource conservation, contentcaching, and/or traffic management.

FIGS. 5-6 illustrate example logic flow diagrams for optimizingkeepalives by categorizing a keepalive as safe or unsafe andtransmitting an unsafe keepalive from a mobile device to the network,while blocking a safe keepalive from going out to the network.

FIG. 7 illustrates an example logic flow diagram for optimizingkeepalive traffic by advancing a keepalive from its expected schedule.

FIG. 8 illustrates an example logic flow diagram for optimizingkeepalive traffic by delaying a keepalive beyond the keepalive period.

FIGS. 9-11 illustrate example logic flow diagrams for optimizingbackground traffic by delaying repeatable background requests.

FIG. 12 shows a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

DETAILED DESCRIPTION

Embodiments of the present disclosure include systems and methods foroptimizing keepalives and other background traffic from mobileapplications on mobile devices to reduce energy consumption, bandwidthconsumption and signaling in wireless networks.

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding of the disclosure. However, in certaininstances, well-known or conventional details are not described in orderto avoid obscuring the description. References to one or an embodimentin the present disclosure can be, but not necessarily are, references tothe same embodiment; and, such references mean at least one of theembodiments.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but not other embodiments.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms may be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any oneor more of the terms discussed herein, nor is any special significanceto be placed upon whether or not a term is elaborated or discussedherein. Synonyms for certain terms are provided. A recital of one ormore synonyms does not exclude the use of other synonyms. The use ofexamples anywhere in this specification including examples of any termsdiscussed herein is illustrative only and is not intended to furtherlimit the scope and meaning of the disclosure or of any exemplifiedterm. Likewise, the disclosure is not limited to various embodimentsgiven in this specification.

Without intent to limit the scope of the disclosure, examples ofinstruments, apparatus, methods and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles may be used in the examples for convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, all technical and scientific terms used herein havethe same meaning as commonly understood by one of ordinary skill in theart to which this disclosure pertains. In the case of conflict, thepresent document, including definitions, will control.

Various embodiments for optimizing network transactions or periodictransactions in wireless networks including mobile networks and wirelesslocal area networks are disclosed herein. Network transactions caninclude keepalive transactions and other periodic transactions. Networktransactions can also include background transactions which can beperiodic. The methodologies and techniques for optimizing keepalive andother background traffic disclosed herein can be implemented by a localproxy or client-side proxy residing on a mobile device in oneembodiment. In another embodiment, an application can implement thekeepalive and other background traffic optimization methodologies andtechniques.

Embodiments of the present disclosure are based on Transport ControlProtocol (TCP) streaming optimization. Application level protocols suchas HTTP (with or without SSL encapsulation) are well understood andnonproprietary. However, an increasing amount of mobile traffic ismoving from the HTTP space to vendor-specific proprietary protocols. Forexample, GOOGLE, WHATSAPP, SKYPE, YAHOO MAIL 2.0 and the like useproprietary protocols. The embodiments of the present disclosure utilizean architecture that is able to optimize traffic over both proprietaryand nonproprietary protocols. In one embodiment, TCP stream is passed asa byte stream from an application to a local proxy (TCP session 1) andfrom the local proxy to host/application/content server (TCP session 2).The application is allowed to establish the necessary handshakes, andthe local proxy observes patterns within the stream. Instead of, or inaddition to, identifying transactions based on HTTP headers and otherprotocol specificity, transactions are identified based on idle periodsbetween them, without requiring any protocol-specific understanding ofthe binary stream. The content similarity is established at basic levelby exact binary match, and binary-level normalizations can be applied toaccommodate protocol-specificities, where they are known.

Embodiments disclosed herein can utilize TCP streaming optimization toidentify transactions within a TCP stream and can further categorizethose transactions as (1) keepalives or heartbeats, (2) other background(or non-user-interactive) or (3) user-interactive. The categorization oftransactions within a TCP stream can be used to optimize keepalive andbackground traffic in a wireless network to reduce signaling andconserve resources of the client device and the wireless network towhich the client device is connected.

Keepalive transactions are transactions that seem to be there with noother purpose than to keep a TCP connection alive. Keepalives can beidentified based on a combination of parameters, including, but notlimited to: periodicity, size thresholds, and similar/repeating contentbased on the knowledge of the actual application level protocol or thelike. In one embodiment, keepalives can be detected in real-time forkeepalive optimization. Various algorithms can be used to detectkeepalives. For example, one example keepalive detection algorithmleverages traffic reports to perform detection retrospectively. Anotherkeepalive detection algorithm can use network messages and/orapplication profiles to detect keepalives as they occur and takeactions. Various algorithms for detecting or identifying keepalives aredisclosed in a related application Ser. No. 61/836,039 titled“IDENTIFICATION AND REPORTING OF KEEP ALIVE MESSAGES AND OTHER NON-USERINTERACTIVE TRAFFIC IN A MOBILE NETWORK” filed on Jun. 17, 2013(Attorney Docket No. 076443-8173.US02), which is expressly incorporatedby reference herein.

Other background traffic and user interactive traffic can bedistinguished from each other based on indications or proxies of useractivity alone or in combination with information such as status of theapplication performing the data transfer (e.g., foreground/background,active, non-active), status of output mechanisms, such as screen, audio,notification LED, Bluetooth, NFC, RFID, touch sensor, any other types ofsensors, camera, etc., readings from the any other sensors or detectorsof the device, such as microphone, accelerometer, biosensors, gyroscope,location sensors, motion sensors, or the like. For example, a requestthat is generated while a screen of a mobile device is off is an exampleof a background request because the request occurred when the mobiledevice was not being actively used by a user (i.e., the device was onbackground mode). By way of another example, a request that occurs whenthere is no user activity and the radio is off (or radio state is idle)is also a background request. On the other hand, a request from anapplication that a user is interacting with is an example of auser-interactive request.

As used herein, a background request from an application on a mobiledevice includes a request that occurs when a user is not actively usingthe application (i.e., the application is in the background mode) or notactively using the mobile device (i.e., the mobile device is in thebackground mode). As used herein, a user-interactive request from anapplication on a mobile device includes a request that occurs when auser is actively interacting with the application or the user isexpecting a response to the request.

Embodiments of the present disclosure also include systems and methodswhich facilitate management of traffic, content caching, and/or resourceconservation between mobile devices (e.g., wireless devices) and anapplication server or content provider.

In one embodiment, optimizing keepalives includes identifying andblocking unnecessary keepalives. Keepalives can be identified orpredicted as being “unnecessary” (or safe to block or simply “safe”)based on various criteria. In one embodiment, safe keepalives arekeepalives whose following transactions are also the same keepalives(e.g., same/similar byte sizes). In one embodiment, a keepalive is safeif other traffic (e.g., from the same or different applications) isoccurring on the same socket or any presence of any traffic from thesame application is detected. In one embodiment, necessary (or unsafe toblock or simply “unsafe”) keepalives are keepalives whose followingtransactions are not the same keepalives (e.g., byte sizes may bedifferent). For example, a keepalive may be necessary, if user activityand/or non-keepalive data for the given application is detected oranticipated in the TCP stream before the next keepalive. In this case,if the first keepalive is eliminated, the connection may not beavailable for the non-keepalive data when such data is to be sent. Inone embodiment, as keepalives themselves may carry payload data, useractivity after such a keepalive may be an indication that a keepalivedid carry payload data and was thus not necessary. In many instances,retrospective observation of traffic patterns may be used to learnsafe/unsafe characteristics of keepalives and use such information toevaluate subsequent keepalive transactions.

In one embodiment, keepalives that are identified as being safekeepalives can be blocked, while keepalives that are identified asunsafe keepalives can be allowed to go out to the network. A flexibleparameter can be utilized to adjust the aggressiveness with whichkeepalives are identified as safe or unsafe.

Referring to FIG. 1A-1, an example schematic diagram depictingoptimization of keepalives by categorizing a keepalive as safe or unsafeand transmitting an unsafe keepalive while blocking a safe keepalive isillustrated. A mobile device 150 coupled to a network 106 includesmobile applications, some of which may utilize keepalives (KAs) tomaintain a long-lived connection. As shown, a keepalive optimizer (e.g.,keepalive optimizer 300 which can be a component of a local proxy 175 inthe mobile device 150 of FIG. 1C) of the mobile device 150 detects KA1and KA2 from application 1 and application 2 respectively at block 102.The keepalive optimizer categorizes KA1 as unsafe and KA2 as safe basedon prediction (or other criteria) at block 114. Based on suchcategorization, the keepalive optimizer allows the unsafe KA1 to go tothe network 106 (i.e., go to its destination server across the network106). As for KA2 that was categorized as safe, the keepalive optimizerblocks it at block 118, preventing KA2 from reaching its destinationserver. As illustrated by this example, by identifying which keepalivesare necessary and which ones are unnecessary, the keepalive optimizer ofthe present disclosure can reduce the keepalive traffic and conserveresources in the mobile device 150 and the network 106.

In addition to some of the methods of categorization or classificationof keepalives as safe or unsafe discussed above, in one embodiment, thekeepalive optimizer can utilize a predictive method to learn and blocksafe keepalives. In this embodiment, “long enough” keepalives, i.e., thelong unnecessary keepalive chains that out-benefit potential cost ofblocking such as TCP re-establishment, and other unknown cost due touser inconvenience or application's behavior can be detected and/orblocked. Blocking unnecessary keepalives can include three stagesincluding observing traffic for a learning period (e.g., either for asingle device run-time, or for multiple devices centrally) to determinefactors that can be used to perform strongest prediction of necessity(i.e., factors for predicting whether a keepalive is necessary orunnecessary). Such factors can include user, application,time-of-the-day, day-of-the-week, screen state pattern, number ofnon-necessary keepalives in the immediate past and a number of othersfeatures and/or parameters. The second stage includes the execution,where the necessary keepalives are allowed to go out to the networknormally, while the unnecessary keepalives are blocked. The third stageinvolves validation, where traffic following the blocking event isobserved to determine, for example, whether a keepalive that waspredicted to be unnecessary was actually unnecessary.

In one embodiment, the predictive method for learning and blocking safekeepalives is based on decision list learning. The method utilizespredictors listed in Table 1 and confidence parameters listed on Table 2for determining a rule set that can isolate safe to block keepalives(i.e., safe KA) from unsafe to block keepalives (i.e., unsafe KA). Thepredictors can be collected for every detected keepalive peruser/application. “Current” is used herein to describe the keepalivebeing detected. These are recorded in an analysis field in the netlog.These keepalive data can be stored in a persistent local databasestorage (e.g., database 310 in FIG. 3A). The stored keepalive data canbe used for learning. Old keepalive data can be flushed out from time totime.

TABLE 1 Keepalive Predictors Parameter name, short Data AcronymPredictor Type Form Explanation 1 Hour integer F1, H The currentkeepalive's transaction log time's local hour. 2 AfterOnScreen binaryF2, E There was an onscreen activity between last keepalive detected andthe current keepalive. 3 Saferun integer F3, SR The length ofunnecessary keepalive sequences before the current keepalive. If this isthe first keepalive in the current TCP session, this is 0. 4 Intervalsinteger F4, I The UNIX epoch difference between the current keepaliveand last keepalive 5 OnScreenDistance integer F5, OSD The UNIX epochdifference between the current keepalive and the last on screen activity6 Bytes integer F6, B The keepalive's transaction log's Fromapp bytes +Fromnet bytes 7 TCP Session integer F7, CO In the current TCP session,the ORDER order of the current keepalive 8 DayOfWeek integer F8, DW Thecurrent keepalive's log time's LOCAL day of week 9 Unnecessary integerF9, UCL This is going to be recorded not Chain Length when the keepaliveis detected but after the end of successive unnecessary keepalives; forevery keepalive that belongs to the current unnecessary keepalives, thefinal unnecessary chain length is recorded. 10 Decision binary R1, D:After learning, whether the current keepalive is blocked or not 11Probability integer R2, P After learning, the probability for theDecision 12 Rule formatted R3, R After learning, the rule applied output(Feature (1-8), Equality (−1<=, 0, =, 1>), Value (integer))

TABLE 2 Keepalive Confidence Parameters Parameter name, short ConfidenceAcronym Parameter Data type Form Explanation 1 Minimal integer P1, MCLThe minimally beneficial Expected unnecessary chain length to coverUnnecessary the potential cost of TCP Chain Length reestablishment andother unknown costs. 2 Confidence integer P2, P The minimal confidenceprobability probability of the prediction 3 Training Period integer P3,T Minimal number of keepalives for the application/local proxy to act on4 Data Validity integer P4, V Maximal days for the Periodapplication/local proxy to keep the keepalive data 5 Maximum Blockinteger P5, X How long can a successive Length blocking work 6 KeepaliveP6, A Applications for which keepalive Blocking blocking can be appliedApplicable Apps

After gathering the minimal number of keepalives (P3), the keepaliveoptimizer implementing a decision list learning and blocking algorithminitiates rule learning from a collection of keepalive data having atleast some of the features listed in Table 1 above. From the keepalivedata collection, those keepalives that satisfy F9(UCL)>P1 can beidentified as safe keepalives (i.e., safe KAs), and those keepalivesthat satisfy F9(UCL)<=P1 can be identified as unsafe keepalives (i.e.,unsafe KAs). FIG. 1A-5 shows an example collection of keepalive data,identified as safe KAs and unsafe KAs, specific to a user/applicationand retrieved from a persistent database storage (e.g., database storage310 in FIG. 3A). In one example embodiment, the keepalive optimizerdetermines a rule set that covers only safe KAs by applying one or moreconstraints. For example, when an initial constraint C1 can be appliedto isolate at least some of the safe KAs from unsafe KAs. In the exampleof FIG. 1A-6, the constraint F3(Saferun)>3 has been applied and itcovers only safe KAs as shown. The keepalive optimizer has thus learnedthe first rule including the constraint F3(Saferun)>3. The safe KAscovered by the first rule are then eliminated from the collection ofkeepalive data and the process is repeated with remaining data.

For example, as shown in FIG. 1A-7, another constraint (OSD, >, 10000)has been applied, and it covers not only some safe KAs but also manyunsafe KAs. The keepalive optimizer then applies another constraint (H,=, 2, 3, 5, 6) in addition to (O, >, 10000), which isolates the safe KAsfrom the unsafe KAs as shown in FIG. 1A-8. All or at least some of thepredictors can be evaluated by the keepalive optimizer in learningrules. For example, as shown in FIG. 1A-9, the constraint (Bytes, <,1000) does not completely isolate the safe KAs from the unsafe KAs. Whenno other constraint can effectively isolate safe KAs from unsafe KAs,the rule learning process stops. The end decision list in the aboveexample includes a rule set comprising the following two rules:

-   Rule 1: (SR, >, 3)-   Rule 2: ((OSD, >, 10000), (H, =, 2, 3, 5, 6))

The keepalive optimizer can arrange the learned rules in an order andsequentially apply the learned rules to a new keepalive to determinewhether the new keepalive can be blocked. In one embodiment, thekeepalive optimizer calculates a rule's probability of success comparedto a confidence probability threshold (P2) to determine whether to allowthe rule set to be applied in categorizing a keepalive as safe orunsafe.

In one embodiment, the keepalive optimizer can implement a binarydecision learning algorithm to learn and block a keepalive. For example,long unnecessary keepalive chains can be learned and as soon as akeepalive is detected, the disclosed technology can decide if thekeepalive is going to be long or not (e.g., is the unnecessary keepalivechain length greater than a threshold (e.g., 5)). If the detectedkeepalive is going to be longer than the minimal unnecessary keepalivechain length, the keepalive optimizer decides to block the keepalive.

In one embodiment, the binary decision learning algorithm as part of thelearning process puts each keepalive train into bins. Starting with Hourbins (24 bins) for example, the algorithm determines if any of the binsare not homogenous. A bin is homogenous if every keepalive train in thebin is in the same category, i.e., necessary or unnecessary. If any ofthe bins is not homogenous, the algorithm splits the bin based onsplitting points such as afteronscreen, bytes (fromapp and fromnet),onscreendistance, intervals, CSM order, weekday, or the like. When a newkeepalive is detected, the binary decision learning algorithm puts thekeepalive into the corresponding bin (e.g., hour/afteronscreen/bytes>3bin) and follows the majority in the bin to determine whether to blockor unblock the keepalive. If there is no clear majority or not enoughprior chains, blocking is prevented.

In one embodiment, optimizing keepalives includes identifying andblocking keepalives by blocking application. In one embodiment,keepalives can be identified based on parameters such as, but notlimited to: periodicity, size thresholds, similar/repeating content,knowledge of the actual application level protocol, applications thatare keepalive heavy (e.g., applications that send keepalivesfrequently), or a combination thereof. Applications that exhibit certainkeepalive behavior can then be blocked using one or more keepaliveblocking policies which can be managed by a policy enforcement module.Based on the blocking policies, certain type of keepalive behavior canbe blocked. For example, applications that are keepalive heavy orexhibits a certain keepalive behavior can be blocked for a given percentof keepalive periods. In one embodiment, blocking the applications toblock the keepalives can include blocking specific ports for the givenpercent of keepalive periods. In some instances, this blocking strategymay have a user-impact, cause additional bytes, and/or cause impactsbeyond keepalives. The blocking strategy can be refined by using some ofthe other keepalive optimization methods described in the presentdisclosure.

In one embodiment, keepalives can be optimized by executing them inadvance of their expected schedule as shown in the example schematicdiagram of FIG. 1A-2. In this embodiment, a keepalive period (T_(KA))for an application Y on a mobile device 150 can be identified and aperiod T_(pull-in) for the application Y can be defined, where periodT_(pull-in) is a period to pull a keepalive in from its expectedschedule.

T_(pull-in) can be determined using multiple mechanisms. In oneembodiment, T_(pull-in) is a value that is selected to minimize theadditional time connected (as transmitting more data even if the radiois already up can slightly increase the length of a transaction) andincreased battery consumption (as CPU consumption of more frequenttransactions increases slightly) while also minimizing the number ofinstances where radio needs to be turned on (and cause an additionalconnection) because the end of the allowed period is reached. This canbe done dynamically by observing the realized traffic pattern on eachdevice and weighting potential negative time connected/batteryprobability against probability for additional connections (which alsoresults in additional time connected and battery consumption). This canbe done on an ongoing basis using previous X hours as the sample, orlearning over a longer period of time, utilizing, for example,time-of-the-day, day-of-the-week and screen state as additionalparameters to estimate the probabilities. Alternatively, the same valuecan be used for all users, that would optimize the probability acrossthe entire user base.

After a socket for the application Y has been idle for longer thanT_(pull-in) (i.e., T_(idle)>T_(pull-in)) and a keepalive optimizerdetects the radio of the mobile device 150 go up at block 135 (i.e.,radio turns on or transitions from an idle state to a connected state,or lower power state to higher power state), the keepalive optimizertriggers a new keepalive 136 which is transmitted to the network 106.The new keepalive 136 is executed before the end of the T_(KA) inadvance of the next expected KA 138.

In one embodiment, the new keepalive 136 is triggered by terminating theconnection or dropping the application socket. When the connection isterminated, application Y attempts to connect to the network 106 bypiggybacking on the radio connection that was already established, whichallows for reduction in signaling. When it is time to send the newkeepalive 136, a new handshake would be needed to establish aconnection, which would result in an increase in bytes transferred. Toavoid additional bytes for handshakes, mechanisms other than droppingthe socket can be used to trigger a new keepalive on a per-applicationbasis. For example, a synthetic keepalive can be created.

In one embodiment, executing keepalive in advance may start either afteridentifying the first keepalive period (T_(KA)), or it can start workingeven before the first successful keepalive period is identified. Thelatter is useful in a case where the network closes the socket withshorter duration than the application sends keepalives and thelong-lived socket would keep closing. This would cause user experienceissues as the socket is not available all the time for pushing data tothe mobile device. By sending the keepalives early even without theapplication being able to make them successfully, the keepaliveoptimizer can keep the long-lived socket alive and make the userexperience better.

In one embodiment, keepalives can be optimized by extending thekeepalive period as shown in the schematic diagram of FIG. 1A-3.

A period X1 and/or pattern Z, and period X2 for application Y can bedefined. A long-lived connection 143 may be established between a socketfor application Y and the network 106. After the socket for applicationY has been idle for longer than X1 (i.e., T_(idle)>X1), or if trafficmatches pattern Z, the keepalive optimizer of the mobile device 150 doesnot send a keepalive detected at block 145 out to the network 108, untileither X2 seconds have passed from the first traffic after X1. Afterthat, the keepalive optimizer sends the latest transaction 152 to thenetwork 106. The latest transaction can be identified based on atransaction boundary defined by a pause (e.g., a few second pause)between a data stream at block 151. Any response from the network isthen relayed back to the application normally. Alternately, when a radiocomes up at block 146 (i.e., radio of the mobile device transitions froma low power state to a high power state or from an idle state to aconnected state) for other reasons (e.g., detection of user-interactivetraffic, data from a remote server) after period X1, the keepaliveoptimizer identifies the latest keepalive transaction a block 147 andsends the keepalive 149 to the network 106.

The delay keeps both the application and server connections healthy andallows for delaying keepalives up to time period X2. By way of example,for applications such as SKYPE, the delay can be as long as 10 seconds,and for applications based on Google Cloud Messaging (GCM), the delaycan be as long as 60 seconds. Extending of the keepalive period orinterval as described herein is beneficial with or without alignmentbetween different applications. For example, keepalive period ofmultiple applications can be extended by different amounts so that allthe keepalives can be sent when the radio of the mobile device comes up.The period X1 or pattern Z and period X2 for the application Y can bedetermined based on offline analysis of the application behavior. Theoffline analysis can be performed on the mobile device 150 or a proxyserver (e.g., proxy server 125) associated with a host server (e.g.,host server 100).

In one embodiment, signaling in a wireless network can be optimized bydelaying certain types of traffic under certain conditions. FIG. 1A-4 isan example schematic diagram that depicts optimization of backgroundtraffic by delaying repeatable background requests on the mobile device150.

Background traffic generated when an application is in the backgroundand when the radio is down can be delayed. Such traffic can be delayeduntil the radio is observed or detected to come up, or until the knownapplication tolerance is about to expire (e.g., 2 minute grace period).The background traffic that is delayed can include different requesttypes (e.g., log uploads, status updates) as well as keepalive traffic.In one embodiment, application tolerance is defined as the shorter ofthe longest period during which the application will not display anerror message to the user and the longest period beyond which theapplication will stop retrying the connection.

In some instances, different tolerances for different request types canbe identified in determining the length of delay. For example, “logupload” request type is typically retried for long periods of time, soit will have a longer tolerance compared to another request type (e.g.,status update). In one embodiment, delaying background requestsaccording to the tolerance can be more advantageous than normalizing thedelay, as the latter can cause the server to start polling theapplication for log uploads. In one embodiment, delaying certain typesof traffic under certain conditions can be generalized beyondper-transaction handling to per-application handling. For example, anybackground requests from an application can be delayed the same amountof time, regardless of the background request type. In one embodiment,delay of background requests can be configured using a policy

In one embodiment, the background request can be a repeatable backgroundrequest, where the application itself has logic to recover from anunsuccessful transaction. This recovery logic can be exploited by thekeepalive optimizer to cause background requests to fail on purpose, andforce the application to use the retry logic on the application layer toeventually execute the background request after a time delay. An exampleimplementation of delaying background traffic for an application (e.g.,FACEBOOK) by the keepalive optimizer will now be described. It should benoted that the keepalive optimizer can be the application itself (inthis example the FACEBOOK) or a local proxy (e.g., local proxy 175).

In one embodiment, traffic patterns associated with an application canbe learned or observed during a learning period. From the observation,it may be determined that the application resends the same requestimmediately when a request does not get a response within a specifictime (e.g., 1 minute, 5 minutes). For example, background requests 1 and2 shown in FIG. 1A-4 are retried after T_(rety-1) and T_(retry-2)respectively when no response is received from the network. Based onthis observation or information, the keepalive optimizer intercepts anddelays the background requests for a specific time (configurable via apolicy management system (PMS)) until a trigger in the form of an eventis detected.

In the example FIG. 1A-4, the background requests 1 and 2 areintercepted at block 160 when certain conditions are met. If thebackground requests 1 and 2 are of different type, a separate delaytimer can be started for each of the request. For example, a delay timerfor background request 1 is started at block 162 for a period ofT_(delay-1) and an independent delay timer for background request 2 isstarted at block 164 for a period of T_(delay-2). At block 166, thekeepalive optimizer can detect an undelay trigger for undelayingbackground request 1 and can then transmit background request 1 to thenetwork 106. Similarly, the keepalive optimizer can detect an undelaytrigger for background request 2 at block 170 and transmit backgroundrequest 2 to the network 106.

In one embodiment, intercepting and delaying of the background requestsoccur under certain conditions. For example, a missed request, which isnot able to be served from a cache with existing logic, is entered intoa delay mode if the following example conditions are satisfied:

-   a) the device is on mobile network;-   b) the device is not in the transparent mode (i.e., a measure only    or observation only mode, that does not affect the traffic flow);-   c) the device screen is off;-   d) the device radio is off; and-   e) the feature is enabled by the Policy Management System (PMS).

Similarly, the undelaying of the request (or exit from delay mode) canbe triggered when at least one of the conditions below is satisfied:

-   a) the screen is on;-   b) the radio is up;-   c) network switched to Wi-Fi;-   d) delay timer is expired;-   e) PMS is disabled; and/or-   f) device switch to transparent mode.

In one embodiment, when the background request first gets delayed, thekeepalive optimizer immediately schedules a timer to indicate a delaycycle has started. During the delay cycle, any new background requestsfrom the application are delayed until an undelay event (or an eventthat causes an exit from delay mode) is triggered. If there is notrigger other than delay timer, the keepalive optimizer allows the veryfirst background request after the delay timer expiration to go out tothe network. On the other hand, any other trigger events can cancel thescheduled delay timer. When the trigger for undelay is fired, thekeepalive optimizer goes through all the application requests in thedelay mode and forces their execution immediately.

In one embodiment, the keepalive optimizer can allow some backgroundtransactions to time out, in case the application associated with thebackground transaction is observed to retry the same transaction withoutimpact to functionality or end user experience. In such a case, thestarting point of the timer (or counter) for the delay is the same forthe first background request and the subsequent background requests.Alternately, as described with respect to FIG. 1A-4, a separate timercan be started separately for each background request.

In one embodiment, the keepalive optimizer can delay background traffic,even if the same session (e.g., TCP socket) includes user-interactivetraffic, or background traffic that has shorter tolerance for delays(e.g., if _(Tdelay-1) and _(Tdelay-2) in FIG. 1A-4 are different). Thisallows the keepalive optimizer to delay each transaction for a maximumamount that it has tolerance for, for example, by not sending out thelonger-tolerance traffic if a shorter-tolerance traffic needs to go out.

In one embodiment, in order to delay the background requests, DNSrequests can be cached to prevent a DNS request from turning on theradio of the mobile device. In one embodiment, the hosts to which anapplication makes the request can be identified and cached to facilitatebackground requests to be delayed.

In one embodiment, the PMS can be configured to enable or disabledelaying of background requests and/or how long the delay cycle will beapplied. A default value can also be specified (e.g., 300,000 ms, 300 s,5 minutes). In one embodiment, the keepalive optimizer can report dataon request delay value (i.e., how long the request was delayed by thedelay timer) and radio awareness status when a delayed transaction wassent to a server (e.g., application server, proxy or host server). Therequest delay value can be the amount of time (e.g., milliseconds)between the Cache Lookup Query (CLQ) and a cache miss or error (i.e.,MISS or ERR) response in one embodiment. The radio awareness status maybe:

-   0—the transaction was not radio-aware and was not delayed;-   1—the transaction was radio-aware and was released due to a radio up    event;-   2—the transaction was radio-aware but was released due to the timer    expiration;-   3—the transaction was radio-aware but was released due to a screen    on event;-   4—the transaction was radio-aware but was interrupted abnormally by    the keepalive optimizer, application or local proxy (typically due    to a timeout).

FIG. 1B illustrates an example diagram of a system where a host serverfacilitates management of traffic, content caching, and/or resourceconservation between mobile devices (e.g., wireless devices), anapplication server or content provider, or other servers such as an adserver, promotional content server, an e-coupon server or messagingservers such as the Google Cloud Messaging (GCM) server and the ExchangeActiveSync (EAS) server in a wireless network (or broadband network) forresource conservation. The host server can further optimize signaling ina wireless network for traffic utilizing proprietary (non-standard) andnonproprietary (e.g., HTTP) protocols.

The GCM server allows transfer of data from an application server orcontent provider to user devices using XMPP (upstream and downstreami.e., device to cloud and cloud to device). The GCM server can queuemessages and deliver the messages to the target applications on the userdevice. These messages can inform the mobile application that there isnew data to be fetched from the content provider or application serverand/or can include actual data (e.g., instant messages). The EAS serverallows for wireless synchronization of emails, calendars, contacts, andthe like between an exchange server and a mobile device using an XMLbased protocol over HTTP or HTTPS. Various other intermediary ormessaging servers that facilitate communication between applications onclient devices and content provider or application servers arecontemplated.

The client devices 150 can be any system and/or device, and/or anycombination of devices/systems that is able to establish a connection,including wired, wireless, cellular connections with another device, abase station/cell provider 112, a server and/or other systems such ashost server 100 and/or application server/content provider 110. Clientdevices 150 will typically include a display and/or other outputfunctionalities to present information and data exchanged between amongthe devices 150 and/or the host server 100 and/or applicationserver/content provider 110. The application server/content provider 110can be any server including third party servers or service/contentproviders further including advertisement, promotional content,publication, or electronic coupon servers or services. Similarly,separate advertisement servers 120 a, promotional content servers 120 b,and/or e-Coupon servers 120 c as application servers or contentproviders are illustrated by way of example.

For example, the client/mobile devices 150 can include mobile, handheldor portable devices, wireless devices, or non-portable devices and canbe any of, but not limited to, a server desktop, a desktop computer, acomputer cluster, or portable devices, including a notebook, a laptopcomputer, a handheld computer, a palmtop computer, a mobile phone, acell phone, a smart phone, a PDA, a Blackberry device, a Palm device,any tablet, a phablet (a class of smart phones with larger screen sizesbetween a typical smart phone and a tablet), a handheld tablet (e.g., aniPad, the Galaxy series, the Nexus, the Kindles, Kindle Fires, anyAndroid-based tablets, Windows-based tablets, or any other tablet), anyportable readers/reading devices, a hand held console, a hand heldgaming device or console, a head mounted device, a head mounted display,a thin client or any SuperPhone such as the iPhone, and/or any otherportable, mobile, hand held devices, or fixed wireless interface such asa M2M device, etc. In one embodiment, the client devices 150 (or mobiledevices 150), host server 100, and application server 110 are coupledvia a network 106 and/or a network 108. In some embodiments, the devices150 and host server 100 may be directly connected to one another.

The input mechanism on client devices 150 can include touch screenkeypad (including single touch, multi-touch, gesture sensing in 2D or3D, etc.), a physical keypad, a mouse, a pointer, a track pad, a stylus,a stylus detector/sensor/receptor, motion detector/sensor (e.g.,including 1-axis, 2-axis, 3-axis accelerometer, etc.), a facedetector/recognizer, a retinal detector/scanner, a light sensor,capacitance sensor, resistance sensor, temperature sensor, proximitysensor, a piezoelectric device, device orientation detector (e.g.,electronic compass, tilt sensor, rotation sensor, gyroscope,accelerometer), or any combination of the above.

Signals received or detected indicating user activity at client devices150 through one or more of the above input mechanisms, or others, can beused in the disclosed technology in acquiring context awareness at theclient device 150. Context awareness at client devices 150 generallyincludes, by way of example but not limitation, client device 150operation or state acknowledgement, management, useractivity/behavior/interaction awareness, detection, sensing, tracking,trending, and/or application (e.g., mobile applications) type, behavior,activity, operating state, etc.

Context awareness in the present disclosure also includes knowledge anddetection of network side contextual data and can include networkinformation such as network capacity, bandwidth, traffic, type ofnetwork/connectivity, and/or any other operational state data. Networkside contextual data can be received from and/or queried from networkservice providers (e.g., cell provider 112 and/or Internet serviceproviders) of the network 106 and/or network 108 (e.g., by the hostserver and/or devices 150). In addition to application context awarenessas determined from the client 150 side, the application contextawareness may also be received from or obtained/queried from therespective application/service providers 110 (by the host 100 and/orclient devices 150).

The host server 100 can use, for example, contextual informationobtained for client devices 150, networks 106/108, applications (e.g.,mobile applications), application server/provider 110, or anycombination of the above, to manage the traffic in the system to satisfydata needs of the client devices 150 (e.g., to satisfy application orany other request including HTTP request). In one embodiment, thetraffic is managed by the host server 100 to satisfy data requests madein response to explicit or non-explicit user 103 requests (e.g., viauser interface 104) and/or device/application maintenance tasks. Thetraffic can be managed such that network consumption (e.g., use of thecellular network) is conserved for effective and efficient bandwidthutilization. In addition, the host server 100 can manage and coordinatesuch traffic in the system such that use of device 150 side resources(e.g., including but not limited to battery power consumption, radiouse, processor/memory use) are optimized with a general philosophy forresource conservation while still optimizing performance and userexperience. The host server 100 may also indirectly manage traffic viacreation, selection and/or deployment of traffic blocking policy forimplementation on the mobile device in some embodiments.

For example, in context of battery conservation, the device 150 canobserve user activity (for example, by observing user keystrokes,backlight status, or other signals via one or more input mechanisms,etc.) and alter device 150 behaviors. The device 150 can also requestthe host server 100 to alter the behavior for network resourceconsumption based on user activity or behavior.

In one embodiment, the traffic management for resource conservationand/or keepalive optimization/algorithms for signaling optimization isperformed using a distributed system between the host server 100 andclient device 150. The distributed system can include proxy server andcache components on the server side 100 and on the device/client side,for example, as shown by the server cache 135 on the server 100 side andthe local cache 185 on the client 150 side. In one embodiment, thetraffic management for reducing signaling in the network and reducing oralleviating network congestion can be implemented on the mobile device150 without any support from the server-side proxy or other network-sidecomponents.

Functions and techniques disclosed for context aware traffic managementand keepalive algorithms for resource conservation and reducing oroptimizing signaling in networks (e.g., network 106 and/or 108) anddevices 150, reside in a distributed proxy and cache system. The proxyand cache system can be distributed between, and reside on, a givenclient device 150 in part or in whole and/or host server 100 in part orin whole. The distributed proxy and cache system are illustrated withfurther reference to the example diagram shown in FIG. 1C. Functions andtechniques performed by the proxy and cache components in the clientdevice 150 and the related components therein are described,respectively, in detail with further reference to the examples of FIG.2A.

In one embodiment, client devices 150 communicate with the host server100 and/or the application server 110 over network 106, which can be acellular network and/or a broadband network. To facilitate overalltraffic management between devices 150 and various applicationservers/content providers 110 to implement network (bandwidthutilization) and device resource (e.g., battery consumption), the hostserver 100 can communicate with the application server/providers 110over the network 108, which can include the Internet (e.g., a broadbandnetwork).

In general, the networks 106 and/or 108, over which the client devices150, the host server 100, and/or application server 110 communicate, maybe a cellular network, a broadband network, a telephonic network, anopen network, such as the Internet, or a private network, such as anintranet and/or the extranet, or any combination thereof. For example,the Internet can provide file transfer, remote login, email, news, RSS,cloud-based services, instant messaging, visual voicemail, push mail,VoIP, and other services through any known or convenient protocol, suchas, but not limited to the TCP/IP protocol, UDP, HTTP, DNS, FTP, UPnP,NSF, ISDN, PDH, RS-232, SDH, SONET, etc.

The networks 106 and/or 108 include any collection of distinct networksoperating wholly or partially in conjunction to provide connectivity tothe client devices 150 and the host server 100 and may appear as one ormore networks to the serviced systems and devices. In one embodiment,communications to and from the client devices 150 can be achieved by anopen network, such as the Internet, or a private network or broadbandnetwork, such as an intranet and/or the extranet. In one embodiment,communications can be achieved by a secure communications protocol, suchas secure sockets layer (SSL) or transport layer security (TLS).

In addition, communications can be achieved via one or more networks,such as, but not limited to, one or more of WiMax, a Local Area Network(LAN), Wireless Local Area Network (WLAN), a Personal area network(PAN), a Campus area network (CAN), a Metropolitan area network (MAN), aWide area network (WAN), a Wireless wide area network (WWAN), or anybroadband network, and further enabled with technologies such as, by wayof example, Global System for Mobile Communications (GSM), PersonalCommunications Service (PCS), Bluetooth, WiFi, Fixed Wireless Data, 2G,2.5G, 3G (e.g., WCDMA/UMTS-based 3G networks), 4G, IMT-Advanced, pre-4G,LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks,enhanced data rates for GSM evolution (EDGE), General packet radioservice (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, HSPA+,UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS,extensible messaging and presence protocol (XMPP), real time messagingprotocol (RTMP), instant messaging and presence protocol (IMPP), instantmessaging, USSD, IRC, or any other wireless data networks, broadbandnetworks, or messaging protocols.

FIG. 1C illustrates an example diagram of a proxy and cache systemdistributed between the host server and device which facilitates networktraffic management between a device, an application server or contentprovider, or other servers such as an ad server, promotional contentserver, an e-coupon server or messaging servers such as the GCM serverand the EAS server for resource conservation and content caching. Theproxy system distributed among the host server and the device canfurther optimize signaling in a wireless network for traffic utilizingproprietary (non-standard) and nonproprietary (e.g., HTTP) protocols.

The distributed proxy and cache system can include, for example, theproxy server 125 (e.g., remote proxy) and the server cache 135components on the server side. The server-side proxy 125 and cache 135can, as illustrated, reside internal to the host server 100. Inaddition, the proxy server 125 and cache 135 on the server-side can bepartially or wholly external to the host server 100 and in communicationvia one or more of the networks 106 and 108. For example, the proxyserver 125 may be external to the host server and the server cache 135may be maintained at the host server 100. Alternatively, the proxyserver 125 may be within the host server 100 while the server cache 135is external to the host server 100. In addition, each of the proxyserver 125 and the server cache 135 may be partially internal to thehost server 100 and partially external to the host server 100. Theapplication server/content provider 110 can be any server includingthird-party servers or service/content providers further includingadvertisement, promotional content, publication, or electronic couponservers or services. Similarly, separate advertisement servers 120A,promotional content servers 120B, e-Coupon servers 120C, and/ormessaging servers (e.g., GCM, EAS servers) 120D as application serversor content providers are illustrated by way of example.

The distributed system can also include, in one embodiment, client-sidecomponents, including by way of example but not limitation, a localproxy 175 (e.g., a mobile client on a mobile device) and/or a localcache 185, which can, as illustrated, reside internal to the device 150(e.g., a mobile device).

In addition, the client-side proxy 175 and local cache 185 can bepartially or wholly external to the device 150 and in communication viaone or more of the networks 106 and 108. For example, the local proxy175 may be external to the device 150 and the local cache 185 may bemaintained at the device 150. Alternatively, the local proxy 175 may bewithin the device 150 while the local cache 185 is external to thedevice 150. In addition, each of the proxy 175 and the cache 185 may bepartially internal to the host server 100 and partially external to thehost server 100.

In one embodiment, the distributed system can include an optionalcaching proxy server 199. The caching proxy server 199 can be acomponent which is operated by the application server/content provider110, the host server 100, or a network service provider (e.g., 112), andor any combination of the above to facilitate network traffic managementfor network and device resource conservation. Proxy server 199 can beused, for example, for caching content to be provided to the device 150,for example, from one or more of, the application server/provider 110,host server 100, and/or a network service provider. Content caching canalso be entirely or partially performed by the remote proxy 125 tosatisfy application requests or other data requests at the device 150.

In context-aware traffic management and optimization for resourceconservation and/or keepalive optimization in signaling optimization ina network (e.g., cellular or other wireless networks), characteristicsof user activity/behavior and/or application behavior at a mobile device(e.g., any wireless device) 150 can be tracked by the local proxy 175and communicated over the network 106 to the proxy server 125 componentin the host server 100, for example, as connection metadata. The proxyserver 125, which in turn is coupled to the application server/provider110, provides content and data to satisfy requests made at the device150. The local proxy 175 can be a protocol-agnostic component that canidentify a pattern within a byte stream and perform a direct replay ofthe binary transactions in one embodiment. In another embodiment, thelocal proxy 175 can optimize keepalives for signaling optimization in awireless network utilizing proprietary and/or nonproprietary protocols.

In addition, the local proxy 175 can identify and retrieve mobile deviceproperties, including one or more of battery level, network that thedevice is registered on, radio state, signal strength, cell identifier(i.e., cell ID), location area code, or whether the mobile device isbeing used (e.g., interacted with by a user). In some instances, thelocal proxy 175 can delay, expedite (prefetch), and/or modify data priorto transmission to the proxy server 125, when appropriate, as will befurther detailed with references to the description associated with theexamples of FIG. 2A.

The local cache 185 can be included in the local proxy 175 or coupled tothe local proxy 175 and can be queried for a locally stored response tothe data request prior to the data request being forwarded on to theproxy server 125. Locally cached responses can be used by the localproxy 175 to satisfy certain application requests of the mobile device150, by retrieving cached content stored in the cache storage 185, whenthe cached content is still valid.

Similarly, the proxy server 125 of the host server 100 can also delay,expedite, or modify data from the local proxy prior to transmission tothe content sources (e.g., the application server/content provider 110).In addition, the proxy server 125 uses device properties and connectionmetadata to generate rules for satisfying request of applications on themobile device 150. The proxy server 125 can gather real time trafficinformation about requests of applications for later use in optimizingsimilar connections with the mobile device 150 or other mobile devices.

In general, the local proxy 175 and the proxy server 125 are transparentto the multiple applications executing on the mobile device. The localproxy 175 is generally transparent to the operating system or platformof the mobile device and may or may not be specific to devicemanufacturers. In some instances, the local proxy 175 is optionallycustomizable in part or in whole to be device specific. In someembodiments, the local proxy 175 may be bundled into a wireless model, afirewall, and/or a router.

In one embodiment, the host server 100 can in some instances, utilizethe store and forward functions of a short message service center (SMSC)162, such as that provided by the network service provider, incommunicating with the device 150 in achieving network trafficmanagement. Note that SMSC 162 can also utilize any other type ofalternative channel including USSD or other network control mechanisms.The host server 100 can forward content or HTTP responses to the SMSC162 such that it is automatically forwarded to the device 150 ifavailable and for subsequent forwarding if the device 150 is notcurrently available.

In general, the disclosed distributed proxy and cache system allowsoptimization of network usage, for example, by serving requests from thelocal cache 185, the local proxy 175 reduces the number of requests thatneed to be satisfied over the network 106. Further, the local proxy 175and the proxy server 125 may filter irrelevant data from thecommunicated data. In addition, the local proxy 175 and the proxy server125 can also accumulate low priority data and send it in batches toavoid the protocol overhead of sending individual data fragments. Thelocal proxy 175 and the proxy server 125 can also compress or transcodethe traffic, reducing the amount of data sent over the network 106and/or 108. The signaling traffic in the network 106 and/or 108 can bereduced, as the networks are now used less often and the network trafficcan be synchronized among individual applications.

With respect to the battery life of the mobile device 150, by servingapplication or content requests from the local cache 185, the localproxy 175 can reduce the number of times the radio module is powered up.The local proxy 175 and the proxy server 125 can work in conjunction toaccumulate low priority data and send it in batches to reduce the numberof times and/or amount of time when the radio is powered up. The localproxy 175 can synchronize the network use by performing the batched datatransfer for all connections simultaneously. Furthermore, by preventingthe mobile device from constantly attempting to signal the network thatis congested, and/or allowing selective (e.g., high priority) traffictowards the network, the local proxy 175 can conserve battery resourcesof the mobile device.

FIG. 1D illustrates an example diagram of the logical architecture of adistributed proxy and cache system. The distributed system can include,for example the following components:

Client Side Proxy 175: a component installed in a smartphone, mobiledevice or wireless device 150 that interfaces with device's operatingsystem, as well as with data services and applications installed in thedevice. The client side proxy 175 is typically compliant with and ableto operate with standard or state of the art networking protocols.Additional components and features of the client-side proxy 175 areillustrated with further references to the examples of FIG. 2A.

The server side proxy 125 can include one or more servers that caninterface with third-party application servers (e.g., 199), mobileoperator's network (which can be proxy 199 or an additional server thatis not illustrated) and/or the client side proxy 175. In general, theserver side proxy 125 can be compliant with and is generally able tooperate with standard or state of the art networking protocols and/orspecifications for interacting with mobile network elements and/orthird-party servers. In one embodiment, the server-side proxy 125 canutilize the store and forward functions of a short message servicecenter (SMSC) 162 in communicating with the client-side proxy 175 on themobile device 150 to optimize network traffic.

Log Storage and Processing Service (LSPS) 174: The log storage andprocessing service, server, system or component 174 can providereporting and usage analytics services. The LSPS 174 can collectinformation (e.g., logs) from the client side 175 and/or the server side125 and provide the necessary tools for producing reports and usageanalytics that can be used for analyzing traffic and signaling data. Theclient logs (e.g., logs on the client device 150 aggregated by the localproxy 175) are stored in the device until a data channel is activated,and they are then transferred in binary format to the LSPS 174. In oneembodiment, the logs are processed using log processing tools providedby the LSPS 174. The processed logs are subsequently stored in adistributed database. The logs may be used for reporting as well as fortroubleshooting issues. For example, analytics from the logs can be usedby the proxy system in managing, reducing or optimizing network trafficor by the network operator in monitoring their networks for possibleimprovements and enhancements. Note that LSPS 174 as illustrated may bea server separate from the server-side proxy 125, or it may be acomponent of the server-side proxy 125, residing partially or whollytherein.

In one implementation, the level of logging (e.g., types of data to belogged, and the like) can be specified using configuration settings inthe client-side proxy 175 and/or the server-side proxy 125. Various datarelating to bytes and transactions, network connectivity, power,subscriber count, and the like may be logged, and/or processed usingdefault (or other) settings on a periodic (e.g., hourly, daily, and thelike) basis.

Bytes and Transactions data may include a number of bytes transacted(both to and from), the total number of transactions between theclient-side proxy 175 and each application, the client-side proxy 175and the network (e.g., radio access network 112), the client-side proxy175 and its cache, and the like. Network Connectivity data may include,for example, total time the device spends in “data connected” state(based on a two-state connectivity model), total number of transitionsinto the data connected state, the number of times the radio transitionsinto the data connected state due to a network request that was proxiedthrough the client-side proxy 175, total time spent in the dataconnected state due to a network request that was proxied through theclient-side proxy 175, the number of transitions into data connectedmode saved by the client-side and/or server-side proxy system, theamount of time in data connected state saved by the client-side and/orserver-side proxy system, simulated values for the previous four items,as if traffic proxied via client-side and/or server-side proxy systemwere the only traffic on the device. Network connectivity data can alsoinclude the amount of time taken to transition from an idle state toconnected state (i.e., setup time), a baseline or a reference determinedfrom a sample of setup times, and the like. Power-related data mayinclude, for example, each one-percent (or any other percentage value)change in the battery level, the total time the device is powered on butnot connected to a power source, and the like. Subscriber count data mayinclude, for example, the number of new subscribers observed in a periodand the number of active subscribers in the period. This data may beaggregated by the host server, for example. Reporting of the above datacan be done based on variables such as network bearer type (e.g., all,mobile or Wi-Fi), category (e.g., all, device model or applicationname), time (e.g., hour, day or month), and the like, or combinationsthereof.

FIG. 1E illustrates an example diagram showing the architecture ofclient-side components in a distributed proxy and cache system having akeepalive optimizer for optimizing keepalive and other backgroundtraffic in a wireless network.

The client-side proxy 175 components can include software components oragents installed on the mobile device that enable traffic optimizationand perform the related functionalities on the client side. Mobile OSand Apps 165 include components of the client side proxy 175 can operatetransparently for end users and applications 163, and interface with thedevice's operating system (OS) 162. The client side proxy 175 can beinstalled on mobile devices for optimization to take place, and it caneffectuate changes on the data routes and/or timing. Once data routingis modified, the client side proxy 175 can respond to applicationrequests to service providers or host servers, in addition to or insteadof letting those applications 163 access data network directly. Ingeneral, applications 163 on the mobile device will not notice that theclient side proxy 175 is responding to their requests.

Some example components of the client side proxy 175 are described asfollows:

Device State Monitor 121: The device state monitor 121 can beresponsible for identifying several states and metrics in the device,such as network status (e.g., radio on/off status, connected to Wi-Fi,2G, 3G or other mobile network), display status, battery level (e.g.,via the radio/battery information 161), transparent mode status, etc.,such that the remaining components in the client side proxy 175 canoperate and make decisions according to device state, acting in anoptimal way in each state.

Traffic Recognizer 122: The traffic recognizer 122 analyzes all trafficbetween the wireless device applications 163 and their respective hostservers in order to identify recurrent patterns. Supported transportprotocols include, for example, DNS, HTTP and HTTPS, such that trafficthrough those ports is directed to the client side proxy 175. Whileanalyzing traffic, the client side proxy 175 can identify recurringpolling patterns which can be candidates to be performed remotely by theserver side proxy 125, and send to the protocol optimizer 123.

Protocol Optimizer 123: The protocol optimizer 123 can implement thelogic of serving recurrent requests from the local cache 185 instead ofallowing those request go over the network to the serviceprovider/application host server. One of its tasks is to eliminate orminimize the need to send requests to the network, positively affectingnetwork congestion and device battery life.

Local Cache 185: The local cache 185 can store responses to recurrentrequests, and can be used by the Protocol Optimizer 123 to sendresponses to the applications 163.

Traffic Scheduler 124: The traffic scheduler 124 can temporally movecommunications to optimize usage of device resources by unifyingkeepalive signaling so that some or all of the different applications163 can send keepalive messages at the same time (traffic pipelining).Traffic scheduler 124 may also decide to delay transmission of data thatis not relevant at a given time (for example, when the device is notactively used).

The keepalive optimizer 300: The keepalive optimizer 300 can optimizekeepalive and other non-user interactive or background traffic usingvarious methodologies. In one embodiment, the keepalive optimizer 300can improve the efficiency of keepalive transactions and managelong-lived connections between mobile applications and associatedapplication/host servers. For example, the keepalive optimizer 300 canmanage long-lived connections with fewer keepalives, utilizeradio-awareness, application behavior and/or device state to scheduletransmission of keepalives and other background traffic, and the like.By performing these optimizations, the keepalive optimizer 300 canreduce unnecessary traffic in the mobile network, reduce batteryresource consumption on mobile devices, save on bandwidth resourceconsumption and manage long-lived connections among others. Variousaspects of the keepalive optimizer 300 are described in detail in FIG.3A.

Policy Manager 129: The policy manager 129 can store and enforce trafficoptimization and reporting policies provisioned by a Policy ManagementServer (PMS). At the client side proxy 175 first start, trafficoptimization and reporting policies (policy profiles) that are to beenforced in a particular device can be provisioned by the PolicyManagement Server. Enforcing traffic management policies at the device'sIP layer lets an operator manage traffic before it uses radio accessednetwork resources. Policy usage can range from creating highly targetedsubscriber plans to proactively and/or reactively managing networkcongestion. In one implementation, the conditions for selecting a policyfor enforcement, and/or conditions for dropping an implemented policy,may be managed or coordinated by the policy manager 129. For example, insome embodiments, the policy manager 129 can manage and implementkeepalive and other background traffic optimization policies such asblocking policies, delaying policies, transmission policies, and/or thelike configured and provisioned by the PMS. For example, the PMS canhave two policy configurations for optimizing background requests: (1)true to enable the optimization and false to disable the optimizationand (2) length of delay cycle to be applied if there is no other eventtriggering undelay. Similarly, the PMS can provide and the policymanager 129 can implement other configurations for various components ofthe keepalive optimizer 300. In one embodiment, the policy manager 129can receive and implement a policy configuration from the PMS to enableor disable the keepalive optimizer 300 at an application level or at auser or device level.

Watch Dog 127: The watch dog 127 can monitor the client side proxy 175operating availability. In case the client side proxy 175 is not workingdue to a failure or because it has been disabled, the watchdog 127 canreset DNS routing rules information and can restore original DNSsettings for the device to continue working until the client side proxy175 service is restored.

Reporting Agent 126: The reporting agent 126 can gather information(e.g., logs) about the events taking place in the device and send theinformation to the log storage and processing service 174, whichcollects and stores client-side and/or server-side proxy system logs.Event details are stored temporarily in the device and transferred tolog storage and processing service 174 only when the data channel stateis active. If the client side proxy 175 does not send records within aperiod of time (e.g., twenty-four hours), the reporting agent 126 may,in one embodiment, attempt to open the connection and send recordedentries or, in case there are no entries in storage, an empty reportingpacket. All reporting settings may be configured in the policymanagement server (PMS). The information in the logs may be used forreporting and/or troubleshooting, for example.

Push Client 128: The push client 128 can be responsible for the trafficbetween the server side proxy 125 and the client side proxy 175. Thepush client 128 can send out service requests like content updaterequests and policy update requests, and can receive updates to thoserequests from the server side proxy 125. In addition, push client 128can send data to a log storage and processing service 174, which may beinternal to or external to the server side proxy 125.

The proxy server 199 has a wide variety of uses, from speeding up a webserver by caching repeated requests, to caching web, DNS and othernetwork lookups for a group of clients sharing network resources. Theproxy server 199 is optional. The distributed proxy and cache system(125 and/or 175) allows for a flexible proxy configuration using eitherthe proxy 199, additional proxy(s) in operator's network, or integratingboth proxies 199 and an operator's or other third-party's proxy.

FIG. 2A depicts a block diagram illustrating another example ofclient-side components in a distributed proxy and cache system, furtherincluding a proprietary/non-standard protocol adaptation engine and akeepalive optimizer. The client-side components in a distributed proxyand cache system can reside on a mobile device (e.g., wireless device)250 that manages traffic in a wireless network (or broadband network)for keepalive optimization, signaling optimization, resourceconservation, content caching, and/or traffic management. FIG. 2Bdepicts a block diagram illustrating examples of additional componentsshown in the example of FIG. 2A which is further capable of performingmobile traffic categorization and management based on applicationbehavior and/or user activity.

The mobile device 250, which can be a device that is portable or mobile(e.g., any wireless device), such as a portable phone, generallyincludes, for example, a network interface 208, an operating system 204,a context API 206, and mobile applications which may be proxy-unaware210 or proxy-aware 220. Note that while the client device 250 isspecifically illustrated in the example of FIG. 2A as a mobile device,such depiction is not a limitation, and mobile device 250 may be anywireless, broadband, portable/mobile or non-portable device able toreceive and/or transmit signals to satisfy data requests over a networkincluding wired or wireless networks (e.g., Wi-Fi, cellular, Bluetooth,LAN, WAN, and the like).

The network interface 208 can be a networking module that enables thedevice 250 to mediate data in a network with an entity that is externalto the mobile device 250, through any known and/or convenientcommunications protocol supported by the mobile device and the externalentity. The network interface 208 can include one or more of a networkadaptor card, a wireless network interface card (e.g., SMS interface,Wi-Fi interface, interfaces for various generations of mobilecommunication standards including but not limited to 2G, 3G, 3.5G, 4G,LTE, etc.), Bluetooth, or whether or not the connection is via a router,an access point, a wireless router, a switch, a multilayer switch, aprotocol converter, a gateway, a bridge, a bridge router, a hub, adigital media receiver, and/or a repeater.

Device 250 can further include, client-side components of thedistributed proxy and cache system which can include, a local proxy 275(e.g., a mobile client of a mobile device) and a cache 285. In oneembodiment, the local proxy 275 includes a user activity module 215, aproxy API 225, a request/transaction manager 235, a caching policymanager 245 having an application protocol module 248, a traffic shapingengine 255, and/or a connection manager 265. The traffic shaping engine255 may further include an alignment module 256 and/or a batching module257, the connection manager 265 may further include a radio controller266, a heartbeat manager 267 and a keepalive optimizer 300. Therequest/transaction manager 235 can further include an applicationbehavior detector 236 having a prioritization engine 241, a patterndetector 237, an application profile generator 239, a time criticalitydetection engine 242, an application state categorizer 243 and anapplication traffic categorizer 244. In one embodiment, the local proxyor the device can further include a proprietary/non-standard protocoladaptation engine 401 for optimizing traffic in a protocol agnosticmanner.

Additional or less components/modules/engines can be included in thelocal proxy 275 and each illustrated component.

As used herein, a “module,” “manager,” “handler,” “detector,”“optimizer,” “interface,” “controller,” “normalizer,” “generator,”“invalidator,” or “engine” includes a general purpose, dedicated orshared processor and, typically, firmware or software modules that areexecuted by the processor. Depending upon implementation-specific orother considerations, the module, manager, handler, detector, optimizer,interface, controller, normalizer, generator, invalidator, or engine canbe centralized or its functionality distributed. The module, manager,handler, detector, optimizer, interface, controller, normalizer,generator, invalidator, or engine can include general or special purposehardware, firmware, or software embodied in a computer-readable(storage) medium for execution by the processor.

As used herein, a computer-readable medium or computer-readable storagemedium is intended to include all mediums that are statutory (e.g., inthe United States, under 35 U.S.C. 101), and to specifically exclude allmediums that are non-statutory in nature to the extent that theexclusion is necessary for a claim that includes the computer-readable(storage) medium to be valid. Known statutory computer-readable mediumsinclude hardware (e.g., registers, random access memory (RAM),non-volatile (NV) storage, to name a few), but may or may not be limitedto hardware.

In one embodiment, a portion of the distributed proxy and cache systemfor mobile traffic management resides in or is in communication with themobile device 250, including local proxy 275 (mobile client) and/orcache 285. The local proxy 275 can provide an interface on the mobiledevice 250 for users to access device applications and servicesincluding email, IM, voice mail, visual voicemail, feeds, Internet,games, productivity tools, or other applications, etc.

The local proxy 275 is generally application independent and can be usedby applications (e.g., both proxy-aware and proxy-unaware applications210 and 220 and other mobile applications) to open TCP (TransportControl Protocol) or other protocol based connections to a remote server(e.g., the server 100 in the examples of FIG. 1B-1C and/or server proxy125 shown in the examples of FIG. 1B). In some instances, the localproxy 275 includes a proxy API 225 which can be optionally used tointerface with proxy-aware applications 220 (or applications (e.g.,mobile applications) on a mobile device (e.g., any wireless device)).

The applications 210 and 220 can generally include any user application,widgets, software, HTTP-based application, web browsers, video or othermultimedia streaming or downloading application, video games, socialnetwork applications, email clients, RSS management applications,application stores, document management applications, productivityenhancement applications, and the like. The applications can be providedwith the device OS, by the device manufacturer, by the network serviceprovider, downloaded by the user, or provided by others.

One embodiment of the local proxy 275 includes or is coupled to acontext API 206, as shown. The context API 206 may be a part of theoperating system 204 or device platform or independent of the operatingsystem 204, as illustrated. The operating system 204 can include anyoperating system including but not limited to, any previous, current,and/or future versions/releases of, Windows Mobile, iOS, Android,Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc.

The context API 206 may be a plug-in to the operating system 204 or aparticular client/application on the device 250. The context API 206 candetect signals indicative of user or device activity, for example,sensing motion, gesture, device location, changes in device location,device backlight, keystrokes, clicks, activated touch screen, mouseclick or detection of other pointer devices. The context API 206 can becoupled to input devices or sensors on the device 250 to identify thesesignals. Such signals can generally include input received in responseto explicit user input at an input device/mechanism at the device 250and/or collected from ambient signals/contextual cues detected at or inthe vicinity of the device 250 (e.g., light, motion, piezoelectric,etc.).

In one embodiment, the user activity module 215 interacts with thecontext API 206 to identify, determine, infer, detect, compute, predict,and/or anticipate, characteristics of user activity on the device 250.Various inputs collected by the context API 206 can be aggregated by theuser activity module 215 to generate a profile for characteristics ofuser activity. Such a profile can be generated by the user activitymodule 215 with various temporal characteristics. For instance, useractivity profile can be generated in real-time for a given instant toprovide a view of what the user is doing or not doing at a given time(e.g., defined by a time window, in the last minute, in the last 30seconds, etc.), a user activity profile can also be generated for a‘session’ defined by an application or web page that describes thecharacteristics of user behavior with respect to a specific task theyare engaged in on the mobile device 250, or for a specific time period(e.g., for the last 2 hours, for the last 5 hours).

Additionally, characteristic profiles can be generated by the useractivity module 215 to depict a historical trend for user activity andbehavior (e.g., 1 week, 1 mo., 2 mo., etc.). Such historical profilescan also be used to deduce trends of user behavior, for example, accessfrequency at different times of day, trends for certain days of the week(weekends or week days), user activity trends based on location data(e.g., IP address, GPS, or cell tower coordinate data) or changes inlocation data (e.g., user activity based on user location, or useractivity based on whether the user is on the go, or traveling outside ahome region, etc.) to obtain user activity characteristics.

In one embodiment, user activity module 215 can detect and track useractivity with respect to applications, documents, files, windows, icons,and folders on the device 250. For example, the user activity module 215can detect when an application or window (e.g., a web browser or anyother type of application) has been exited, closed, minimized,maximized, opened, moved into the foreground or into the background,multimedia content playback, etc.

In one embodiment, characteristics of the user activity on the device250 can be used to locally adjust behavior of the device (e.g., mobiledevice or any wireless device) to optimize its resource consumption suchas battery/power consumption and more generally, consumption of otherdevice resources including memory, storage, and processing power, and/orfurther optimize signaling in the network. In one embodiment, the use ofa radio on a device can be adjusted based on characteristics of userbehavior (e.g., by the radio controller 266 of the connection manager265) coupled to the user activity module 215. For example, the radiocontroller 266 can turn the radio on or off, based on characteristics ofthe user activity on the device 250. In addition, the radio controller266 can adjust the power mode of the radio (e.g., to be in a higherpower mode or lower power mode) depending on characteristics of useractivity.

In one embodiment, characteristics of the user activity on device 250can also be used to cause another device (e.g., other computers, amobile device, a wireless device, or a non-portable device) or server(e.g., host server 100 in the examples of FIG. 1B-1C) which cancommunicate (e.g., via a cellular or other network) with the device 250to modify its communication frequency with the device 250. The localproxy 275 can use the characteristics information of user behaviordetermined by the user activity module 215 to instruct the remote deviceas to how to modulate its communication frequency (e.g., decreasingcommunication frequency, such as data push frequency if the user isidle, requesting that the remote device notify the device 250 if newdata, changed, data, or data of a certain level of importance becomesavailable, etc.).

In one embodiment, the user activity module 215 can, in response todetermining that user activity characteristics indicate that a user isactive after a period of inactivity, request that a remote device (e.g.,server host server 100 or the network-side proxy 125 in the examples ofFIG. 1B-1C) send the data that was buffered as a result of thepreviously decreased communication frequency.

In addition, or in alternative, the local proxy 275 can communicate thecharacteristics of user activity at the device 250 to the remote device(e.g., host server 100 or the network-side proxy 125 in the examples ofFIG. 1B-1C) and the remote device determines how to alter its owncommunication frequency with the device 250 for network resourceconservation and conservation of resources of the mobile device 250.

One embodiment of the local proxy 275 further includes arequest/transaction manager 235, which can detect, identify, intercept,process and manage data requests initiated on the device 250, forexample, by applications 210 and/or 220, and/or directly/indirectly by auser request. The request/transaction manager 235 can determine how andwhen to process a given request or transaction, or a set ofrequests/transactions, based on transaction characteristics.

The request/transaction manager 235 can prioritize requests ortransactions made by applications and/or users at the device 250, forexample by the prioritization engine 241. Importance or priority ofrequests/transactions can be determined by the request/transactionmanager 235 by applying a rule set, for example, according to timesensitivity of the transaction, time sensitivity of the content in thetransaction, time criticality of the transaction, time criticality ofthe data transmitted in the transaction, and/or time criticality orimportance of an application making the request.

In addition, transaction characteristics can also depend on whether thetransaction was a result of user-interaction or other user-initiatedaction on the device (e.g., user interaction with an application (e.g.,a mobile application)). In general, a time critical transaction caninclude a transaction resulting from a user-initiated data transfer, andcan be prioritized as such. Transaction characteristics can also dependon the amount of data that will be transferred or is anticipated to betransferred as a result of the requested transaction. For example, theconnection manager 265 can adjust the radio mode (e.g., high power orlow power mode via the radio controller 266) based on the amount of datathat will need to be transferred.

In addition, the radio controller 266/connection manager 265 can adjustthe radio power mode (high or low) based on time criticality/sensitivityof the transaction. The radio controller 266 can trigger the use of highpower radio mode when a time-critical transaction (e.g., a transactionresulting from a user-initiated data transfer, an application running inthe foreground, any other event meeting a certain criteria) is initiatedor detected.

In general, the priorities can be set by default, for example, based ondevice platform, device manufacturer, operating system, etc. Prioritiescan alternatively or additionally be set by the particular application;for example, the Facebook application (e.g., a mobile application) canset its own priorities for various transactions (e.g., a status updatecan be of higher priority than an add friend request or a poke request;a message send request can be of higher priority than a message deleterequest), or an email client or IM chat client may have its ownconfigurations for priority. The prioritization engine 241 may includeset of rules for assigning priority.

The prioritization engine 241 can also track network providerlimitations or specifications on application or transaction priority indetermining an overall priority status for a request/transaction.Furthermore, priority can in part or in whole be determined by userpreferences, either explicit or implicit. A user can in general setpriorities at different tiers, such as, specific priorities forsessions, or types, or applications (e.g., comparing a browsing session,a gaming session, and an IM chat session, the user may set a gamingsession to always have higher priority than an IM chat session, whichmay have higher priority than web-browsing session). A user can setapplication-specific priorities, (e.g., a user may set Facebook-relatedtransactions to have a higher priority than LinkedIn-relatedtransactions), for specific transaction types (e.g., for all sendmessage requests across all applications to have higher priority thanmessage delete requests, for all calendar-related events to have a highpriority, etc.), and/or for specific folders.

The prioritization engine 241 can track and resolve conflicts inpriorities set by different entities. For example, manual settingsspecified by the user may take precedence over device OS settings,network provider parameters/limitations (e.g., set in default for anetwork service area, geographic locale, set for a specific time of day,or set based on service/fee type) may limit any user-specified settingsand/or application-set priorities. In some instances, a manualsynchronization request received from a user can override some, most, orall priority settings in that the requested synchronization is performedwhen requested, regardless of the individually assigned priority or anoverall priority ranking for the requested action.

Priority can be specified and tracked internally in any known and/orconvenient manner, including but not limited to, a binaryrepresentation, a multi-valued representation, a graded representationand all are considered to be within the scope of the disclosedtechnology.

TABLE 3 Change Change (initiated on device) Priority (initiated onserver) Priority Send email High Receive email High Delete email LowEdit email Often not (Un)read email Low possible to sync (Low ifpossible) Move message Low New email in deleted items Low Read more HighDownload High Delete an email Low attachment (Un)Read an email Low NewCalendar event High Move messages Low Edit/change Calendar High Anycalendar change High event Any contact change High Add a contact HighWipe/lock device High Edit a contact High Settings change High Searchcontacts High Any folder change High Change a setting High Connectorrestart High (if no Manual send/receive High changes nothing is sent) IMstatus change Medium Social Network Status Updates Medium Auction outbidor change High Severe Weather Alerts High notification Weather UpdatesLow News Updates Low

Table 3 above shows, for illustration purposes, some examples oftransactions with examples of assigned priorities in a binaryrepresentation scheme. Additional assignments are possible foradditional types of events, requests, transactions, and as previouslydescribed, priority assignments can be made at more or less granularlevels, e.g., at the session level or at the application level, etc.

As shown by way of example in the above table, in general, lowerpriority requests/transactions can include updating message status asbeing read, unread, deleting of messages, deletion of contacts; higherpriority requests/transactions can, in some instances include, statusupdates, new IM chat message, new email, calendar eventupdate/cancellation/deletion, an event in a mobile gaming session, orother entertainment related events, a purchase confirmation through aweb purchase or online, request to load additional or download content,contact book related events, a transaction to change a device setting,location-aware or location-based events/transactions, or any otherevents/request/transactions initiated by a user or where the user isknown to be, expected to be, or suspected to be waiting for a response,etc.

Inbox pruning events (e.g., email, or any other types of messages) aregenerally considered low priority and, absent other impending events,generally will not trigger use of the radio on the device 250.Specifically, pruning events to remove old email or other content can be‘piggy backed’ with other communications if the radio is not otherwiseon, at the time of a scheduled pruning event. For example, if the userhas preferences set to ‘keep messages for 7 days old,’ then instead ofpowering on the device radio to initiate deletion of the message fromthe device 250 the moment that the message has exceeded 7 days old, themessage is deleted when the radio is powered on next. If the radio isalready on, then pruning may occur as regularly scheduled.

The request/transaction manager 235 can use the priorities for requests(e.g., by the prioritization engine 241) to manage outgoing traffic fromthe device 250 for resource optimization (e.g., to utilize the deviceradio more efficiently for battery conservation). For example,transactions/requests below a certain priority ranking may not triggeruse of the radio on the device 250 if the radio is not already switchedon, as controlled by the connection manager 265. In contrast, the radiocontroller 266 can turn on the radio such that a request can be sentwhen a request for a transaction is detected to be over a certainpriority level.

In one embodiment, priority assignments (such as that determined by thelocal proxy 275 or another device/entity) can be used to cause a remotedevice to modify its communication with the frequency with the mobiledevice or wireless device. For example, the remote device can beconfigured to send notifications to the device 250 when data of higherimportance is available to be sent to the mobile device or wirelessdevice.

In one embodiment, transaction priority can be used in conjunction withcharacteristics of user activity in shaping or managing traffic, forexample, by the traffic shaping engine 255. For example, the trafficshaping engine 255 can, in response to detecting that a user is dormantor inactive, wait to send low priority transactions from the device 250,for a period of time. In addition, the traffic shaping engine 255 canallow multiple low priority transactions to accumulate for batchtransferring from the device 250 (e.g., via the batching module 257). Inone embodiment, the priorities can be set, configured, or readjusted bya user. For example, content depicted in Table 3 in the same or similarform can be accessible in a user interface on the device 250 and forexample, used by the user to adjust or view the priorities.

The batching module 257 can initiate batch transfer based on certaincriteria. For example, batch transfer (e.g., of multiple occurrences ofevents, some of which occurred at different instances in time) may occurafter a certain number of low priority events have been detected, orafter an amount of time elapsed after the first of the low priorityevent was initiated. In addition, the batching module 257 can initiatebatch transfer of the accumulated low priority events when a higherpriority event is initiated or detected at the device 250. Batchtransfer can otherwise be initiated when radio use is triggered foranother reason (e.g., to receive data from a remote device such as hostserver 100, server-side proxy 125). In one embodiment, an impendingpruning event (pruning of an inbox), or any other low priority events,can be executed when a batch transfer occurs.

In general, the batching capability can be disabled or enabled at theevent/transaction level, application level, or session level, based onany one or combination of the following: user configuration, devicelimitations/settings, manufacturer specification, network providerparameters/limitations, platform-specific limitations/settings, deviceOS settings, etc. In one embodiment, batch transfer can be initiatedwhen an application/window/file is closed out, exited, or moved into thebackground; users can optionally be prompted before initiating a batchtransfer; users can also manually trigger batch transfers.

In one embodiment, the local proxy 275 locally adjusts radio use on thedevice 250 by caching data in the cache 285. When requests ortransactions from the device 250 can be satisfied by content stored inthe cache 285, the radio controller 266 need not activate the radio tosend the request to a remote entity (e.g., the host server 100 as shownin FIG. 1B, the host server 500 as shown in FIG. 5A or a contentprovider/application server such as the server/provider 110 shown in theexamples of FIGS. 1B-1C). As such, the local proxy 275 can use the localcache 285 and the cache policy manager 245 to locally store data forsatisfying data requests to eliminate or reduce the use of the deviceradio for conservation of network resources and device batteryconsumption.

In leveraging the local cache, once the request/transaction manager 235intercepts a data request by an application on the device 250, the localcache repository 285 can be queried to determine if there is any locallystored response, and also determine whether the response is valid. Whena valid response is available in the local cache 285, the response canbe provided to the application on the device 250 without the device 250needing to access the cellular network or wireless broadband network.

If a valid response is not available, the local proxy 275 can query aremote proxy (e.g., the server proxy 125 of FIG. 4) to determine whethera remotely stored response is valid. If so, the remotely stored response(e.g., which may be stored on the server cache 135 or optional cachingserver 199 shown in the example of FIG. 1C) can be provided to themobile device, possibly without the mobile device 250 needing to accessthe cellular network, thus relieving consumption of network resources.

If a valid cache response is not available, or if cache responses areunavailable for the intercepted data request, the local proxy 275, forexample, can send the data request to a remote proxy (e.g., server proxy125 of FIG. 4) which forwards the data request to a content source(e.g., application server/content provider 110 of FIG. 1B), and aresponse from the content source can be provided through the remoteproxy, as will be further described in the description associated withthe example host server 500 of FIG. 4. The cache policy manager 245 canmanage or process requests that use a variety of protocols, includingbut not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/orActiveSync. The caching policy manager 245 can locally store responsesfor data requests in the local database 285 as cache entries, forsubsequent use in satisfying same or similar data requests.

The caching policy manager 245 can request that the remote proxy monitorresponses for the data request and the remote proxy can notify thedevice 250 when an unexpected response to the data request is detected.In such an event, the cache policy manager 245 can erase or replace thelocally stored response(s) on the device 250 when notified of theunexpected response (e.g., new data, changed data, additional data,etc.) to the data request. In one embodiment, the caching policy manager245 is able to detect or identify the protocol used for a specificrequest, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP,XMPP, and/or ActiveSync. In one embodiment, application specifichandlers (e.g., via the application protocol module 248 of the cachingpolicy manager 245) on the local proxy 275 allows for optimization ofany protocol that can be port mapped to a handler in the distributedproxy (e.g., port mapped on the proxy server 125 in the example of FIG.4).

In one embodiment, the local proxy 275 notifies the remote proxy suchthat the remote proxy can monitor responses received for the datarequest from the content source for changed results prior to returningthe result to the device 250, for example, when the data request to thecontent source has yielded same results to be returned to the mobiledevice. In general, the local proxy 275 can simulate application serverresponses for applications on the device 250, using locally cachedcontent. This can prevent utilization of the cellular network fortransactions where new/changed data is not available, thus freeing upnetwork resources and preventing network congestion.

In one embodiment, the local proxy 275 includes an application behaviordetector 236 to track, detect, observe, and/or monitor applications(e.g., proxy-aware and/or unaware applications 210 and 220) accessed orinstalled on the device 250. Application behaviors or patterns indetected behaviors (e.g., via the pattern detector 237) of one or moreapplications accessed on the device 250 can be used by the local proxy275 to optimize traffic in a wireless network needed to satisfy the dataneeds of these applications.

For example, based on detected behavior of multiple applications, thetraffic shaping engine 255 can align content requests made by at leastsome of the applications over the network (wireless network) (e.g., viathe alignment module 256). The alignment module 256 can delay orexpedite some earlier received requests to achieve alignment. Whenrequests are aligned, the traffic shaping engine 255 can utilize theconnection manager to poll over the network to satisfy application datarequests. Content requests for multiple applications can be alignedbased on behavior patterns or rules/settings including, for example,content types requested by the multiple applications (audio, video,text, etc.), device (e.g., mobile or wireless device) parameters, and/ornetwork parameters/traffic conditions, network service providerconstraints/specifications, etc.

In one embodiment, the pattern detector 237 can detect recurrences inapplication requests made by the multiple applications, for example, bytracking patterns in application behavior. A tracked pattern caninclude, detecting that certain applications, as a background process,poll an application server regularly, at certain times of day, oncertain days of the week, periodically in a predictable fashion, with acertain frequency, with a certain frequency in response to a certaintype of event, in response to a certain type user query, frequency thatrequested content is the same, frequency with which a same request ismade, interval between requests, applications making a request, or anycombination of the above, for example.

Such recurrences can be used by traffic shaping engine 255 to offloadpolling of content from a content source (e.g., from an applicationserver/content provider 110 of FIG. 1A) that would result from theapplication requests that would be performed at the mobile device orwireless device 250 to be performed instead by a proxy server (e.g.,proxy server 125 of FIG. 1C) remote from the device 250. Traffic shapingengine 255 can decide to offload the polling when the recurrences matcha rule. For example, there are multiple occurrences or requests for thesame resource that have exactly the same content, or returned value, orbased on detection of repeatable time periods between requests andresponses such as a resource that is requested at specific times duringthe day. The offloading of the polling can decrease the amount ofbandwidth consumption needed by the mobile device 250 to establish awireless (cellular or other wireless broadband) connection with thecontent source for repetitive content polls.

As a result of the offloading of the polling, locally cached contentstored in the local cache 285 can be provided to satisfy data requestsat the device 250 when content change is not detected in the polling ofthe content sources. As such, when data has not changed, applicationdata needs can be satisfied without needing to enable radio use oroccupying cellular bandwidth in a wireless network. When data haschanged and/or new data has been received, the remote entity (e.g., thehost server) to which polling is offloaded, can notify the device 250.

In one embodiment, the local proxy 275 can mitigate the need/use ofperiodic keepalive messages (heartbeat messages) to maintain TCP/IPconnections, which can consume significant amounts of power thus havingdetrimental impacts on mobile device battery life. The connectionmanager 265 in the local proxy (e.g., the heartbeat manager 267) candetect, identify, and intercept any or all heartbeat (keepalive)messages being sent from applications.

The heartbeat manager 267 can prevent any or all of these heartbeatmessages from being sent over the cellular, or other network, andinstead rely on the server component of the distributed proxy system(e.g., shown in FIG. 1C) to generate and send the heartbeat messages tomaintain a connection with the backend (e.g., applicationserver/provider 110 in the example of FIG. 1B).

In some embodiments, the radio state management engine 203 can performthe management and/or policy management of mobile device radio statepromotion or demotion based on buffer, activity and/or device statemonitoring. The radio state management engine 203 can determine whatuser activity and/or data activity should justify a radio statepromotion and communicate the information to the network to beimplemented as a single session, multi-session, or global policy. Thispolicy can be used to execute the appropriate level of throttling toprevent the radio from going to higher powered states when unjustifiedbased on dynamic conditions (e.g., network status, traffic, congestion,user expectations, user behavior, other activity, and the like.).

The local proxy 275 generally represents any one or a portion of thefunctions described for the individual managers, modules, and/orengines. The local proxy 275 and device 250 can include additional orless components; more or less functions can be included, in whole or inpart, without deviating from the novel art of the disclosure.

FIG. 2B illustrates a block diagram depicting additional components in auser activity module and an application behavior detector shown in theexample of FIG. 2A.

One embodiment of the local proxy 175 includes the user activity module215, which further includes one or more of, a user activitydetector/tracker 215 a, a user activity prediction engine 215 b, and/ora user expectation manager 215 c. The application behavior detector 236can further include a prioritization engine 241 a, a time criticalitydetection engine 241 b, an application state categorizer 241 c, and/oran application traffic categorizer 241 d. The local proxy 175 canfurther include a backlight detector 219.

In one embodiment, the application behavior detector 236 may detect,determine, identify, or infer the activity state of an application onthe mobile device 250 from which traffic has originated or is directedto, for example, via the application state categorizer 241 c and/or theapplication traffic categorizer 241 d. The activity state can bedetermined based on whether the application is in a foreground orbackground state on the mobile device (via the application statecategorizer 241 c) since the traffic for a foreground application versusa background application may be handled differently.

In one embodiment, the activity state can be determined, detected,identified, or inferred with a level of certainty of heuristics, basedon the backlight status of the mobile device 250 (e.g., by the backlightdetector 219) or other software agents or hardware sensors on the mobiledevice, including but not limited to, resistive sensors, capacitivesensors, ambient light sensors, motion sensors, touch sensors, and thelike. In general, if the backlight is on, the traffic can be treated asbeing or determined to be generated from an application that is activeor in the foreground, or the traffic is interactive. In addition, if thebacklight is on, the traffic can be treated as being or determined to betraffic from user interaction or user activity, or traffic containingdata that the user is expecting within some time frame.

In one embodiment, the activity state is determined based on whether thetraffic is interactive traffic or maintenance traffic. Interactivetraffic can include transactions from responses and requests generateddirectly from user activity/interaction with an application, and caninclude content or data that a user is waiting or expecting to receive.Maintenance traffic may be used to support the functionality of anapplication which is not directly detected by a user. Maintenancetraffic can also include actions or transactions that may take place inresponse to a user action, but the user is not actively waiting for orexpecting a response.

For example, a mail or message delete action at a mobile device 250generates a request to delete the corresponding mail or message at theserver, but the user typically is not waiting for a response. Thus, sucha request may be categorized as maintenance traffic, or traffic having alower priority (e.g., by the prioritization engine 241 a) and/or is nottime-critical (e.g., by the time criticality detection engine 241 b).

Contrastingly, a mail ‘read’ or message ‘read’ request initiated by auser at the mobile device 250, can be categorized as ‘interactivetraffic’ since the user generally is waiting to access content or datawhen they request to read a message or mail. Similarly, such a requestcan be categorized as having higher priority (e.g., by theprioritization engine 241 a) and/or as being time critical/timesensitive (e.g., by the time criticality detection engine 241 b).

The time criticality detection engine 241 b can generally determine,identify, infer the time sensitivity of data contained in traffic sentfrom the mobile device 250 or to the mobile device from a host server(e.g., host 300) or application server (e.g., app server/content source110). For example, time sensitive data can include, status updates,stock information updates, IM presence information, email messages orother messages, actions generated from mobile gaming applications,webpage requests, location updates, etc. Data that is not time sensitiveor time critical, by nature of the content or request, can includerequests to delete messages, mark-as-read or edited actions,application-specific actions such as an add-friend or delete-friendrequest, certain types of messages, or other information which does notfrequently change in nature, etc. In some instances when the data is nottime critical, the timing with which to allow the traffic to passthrough is set based on when additional data needs to be sent from themobile device 250. For example, traffic shaping engine 255 can align thetraffic with one or more subsequent transactions to be sent together ina single power-on event of the mobile device radio (e.g., using thealignment module 256 and/or the batching module 257). The alignmentmodule 256 can also align polling requests occurring close in timedirected to the same host server, since these requests are likely to beresponded to with the same data. In some instances, the timing forwithholding or delaying traffic and timing for allowing any delayed ornew traffic to the network can be based on traffic management policies.

In the alternate or in combination, the activity state can be determinedfrom assessing, determining, evaluating, inferring, identifying useractivity at the mobile device 250 (e.g., via the user activity module215). For example, user activity can be directly detected and trackedusing the user activity tracker 215 a. The traffic resulting therefromcan then be categorized appropriately for subsequent processing todetermine the policy for handling. Furthermore, user activity can bepredicted or anticipated by the user activity prediction engine 215 b.By predicting user activity or anticipating user activity, the trafficthus occurring after the prediction can be treated as resulting fromuser activity and categorized appropriately to determine thetransmission policy.

In addition, the user activity module 215 can also manage userexpectations (e.g., via the user expectation manager 215 c and/or inconjunction with the activity tracker 215 a and/or the prediction engine215 b) to ensure that traffic is categorized appropriately such thatuser expectations are generally met. For example, a user-initiatedaction should be analyzed (e.g., by the expectation manager 215 c) todetermine or infer whether the user would be waiting for a response. Ifso, such traffic should be handled under a policy such that the userdoes not experience an unpleasant delay in receiving such a response oraction.

In one embodiment, an advanced generation wireless standard network isselected for use in sending traffic between a mobile device and a hostserver in the wireless network based on the activity state of theapplication on the mobile device for which traffic is originated from ordirected to. An advanced technology standard such as the 3G, 3.5G, 3G+,4G, or LTE network can be selected for handling traffic generated as aresult of user interaction, user activity, or traffic containing datathat the user is expecting or waiting for. Advanced generation wirelessstandard networks can also be selected to transmit data contained intraffic directed to the mobile device which responds to foregroundactivities.

In categorizing traffic and defining a transmission policy for mobiletraffic, a network configuration can be selected for use (e.g., by anetwork configuration selection engine) on the mobile device 250 insending traffic between the mobile device and a proxy server and/or anapplication server (e.g., app server/host 110). The networkconfiguration that is selected can be determined based on informationgathered by the application behavior module 236 regarding applicationactivity state (e.g., background or foreground traffic), applicationtraffic category (e.g., interactive or maintenance traffic), anypriorities of the data/content, time sensitivity/criticality.

In one embodiment, the keepalive optimizer 300 which is described indetail with respect to FIGS. 3A-3D can also detect, identify andintercept keepalives or heartbeat messages and other background trafficusing various optimization methods to reduce keepalive and otherbackground traffic in the mobile network.

FIG. 2C depicts a block diagram illustrating additional components inthe proprietary/non-standard protocol adaptation engine 401 shown in theexample of FIG. 2A. In one embodiment, the proprietary/non-standardprotocol adaptation engine 401 can be a part of the local proxy 275.Alternately, the proprietary/non-standard protocol adaptation engine 401can be implemented separately outside of the local proxy 275.

The proprietary/non-standard protocol adaptation engine 401 can include,for example, a transaction detection engine 272 having a protocolanalyzer 274, a transaction pattern detection engine 276, a binarymatching and normalization engine 278, an application byte streamgenerator 280, a TCP session manager 282 and/or a protocolencoding/decoding module 284. Additional or less modules/engines can beincluded. The various components of the proprietary/non-standardprotocol adaptation engine 401 on the mobile device or user equipment(UE) 250 can singularly or in any combination perform the followingfunctions and features related to signaling optimization in a wirelessnetwork for traffic utilizing proprietary and nonproprietary protocols.

In one embodiment, the local proxy 275 or the proprietary/non-standardprotocol adaptation engine 401 captures the TCP stream from anapplication and passes it on as a byte stream via a byte streaminterface provided by the application byte stream generator 280. A bytestream can be read from or can be written to by an application withouthaving to account for protocol-specific formatting, sizing, and otherdetails.

The TCP session manager 282 can, in one embodiment, manage TCP sessionsincluding establishing of TCP sessions with a proxy server (e.g., proxyserver 125) and/or the content server (e.g., content server 110) andtearing down or termination of TCP sessions. Although the discussion iswith respect to TCP sessions, other similar or session-based protocolsmay be implemented. In one implementation, the TCP session manager 282can establish a first TCP session between an application and the localproxy 275 or the proprietary/non-standard protocol adaptation engine270. The TCP session manager 282 can also establish a TCP sessionbetween the local proxy 275 (or the proprietary/non-standard protocoladaptation engine 270) and a server (e.g., proxy server 125, anapplication or content server 110). Byte streams from the applicationcan be passed over the first TCP session to the keepalive optimizer 300,which can then be sent over to the server over the second TCP session.The TCP session manager 282 may also allow the application to establishthe necessary handshakes.

In one embodiment, the transaction detection engine 272 can detect andidentify transactions based on analysis of the protocol headers andother protocol peculiarities. Such protocol specific analysis can beperformed by a protocol analyzer 274. For example, the protocol analyzer274 can detect transactions in HTTP protocol based on HTTP header,formatting, encoding, and the like.

In another embodiment, the transaction detection engine 272 can beprotocol agnostic, and can detect and/or identify transactions withoutknowing or understanding details of the underlying protocols. Forexample, the transaction detection engine 272 can directly monitor bytestreams captured from applications (e.g., by the application byte streamgenerator 280 interface) and detect and/or identify transactions basedon observed and/or extracted patterns of byte streams and/or matching ordetermining content in byte streams. In one implementation, for example,the transaction pattern detection engine 276 can monitor, detect and/orextract various patterns embedded in byte streams corresponding totransactions from applications. One such pattern can be idle timebetween transactions. The pattern detection engine 276 can monitor bytestreams from an application over time, and detect an idle time of twominutes occurring in between transactions, without knowing orunderstanding the details of the protocol used by the application. Otherpatterns that can be identified or extracted can resemble thoseidentified by the distributed proxy system (e.g., the local proxy 275and/or the proxy server 125) for HTTP or other standard protocols.

In one embodiment, the proprietary/non-standard protocol adaptationengine 401 can include a protocol encoding/decoding module 284. Inimplementations where a binary stream is encapsulated within a securityand/or encryption protocol such as Transport Layer Security (TLS),Secure Sockets Layer (SSL), and the like, the encoding/decoding modulemay include capabilities for decoding such protocols to extract thebinary stream.

FIG. 3A illustrates an example diagram depicting an example ofcomponents in the keepalive optimizer 300 of FIG. 2A.

In optimizing signaling in a wireless network, managing long-livednetwork connections, managing mobile device power usage and/or bandwidthconsumption, one or more keepalive and other background trafficoptimization strategies can be implemented. For example, the keepaliveoptimizer 300 can detect, intercept and categorize keepalives or othernon-interactive or background traffic as safe or unsafe based onpredicted or known impact on user experience or other functionality andselectively block the safe keepalives from going out to the network,thereby reducing the keepalive traffic in the network and conservingbandwidth and power resources. Similarly, the keepalive optimizer 300can execute keepalives in advance of their expected schedules tomaintain long-lived connections or extend keepalive periods to minimizethe number of times the radio of a mobile device needs to turn on andoff and/or the frequency or interval at which keepalives and otherbackground traffic is sent to the network. These keepalive optimizationstrategies can be used alone or in combination to facilitate managementof keepalive and other background traffic, management of connection andresource conservation in mobile networks.

In one embodiment, the keepalive optimizer 300 can reside in the localproxy 275 and operate as part of the local proxy 275. In anotherembodiment, the keepalive optimizer 300 can be included in the operatingsystem (OS) (e.g., as a background service or application that istransparent to the end user) by OS manufacturers or mobile devicemanufacturers (e.g., part of the Android OS, part of the customizedAndroid OS in SAMSUNG smart phones). In yet another embodiment, anapplication (e.g., 210, 220) on the mobile device may include thekeepalive optimizer 300. For example, the keepalive optimizer 300 can bethe application itself. As an example, a messaging application can havea configuration mode that uses keepalives to maintain an always-on IPconnection to the server. The keepalive optimizer 300 in the messagingapplication can then optimize the keepalive traffic while maintainingthe always-on IP connection to the server when the configuration mode isenabled. In other embodiments, a keepalive optimizer 300 on a mobiledevice 250 can be provided by network service providers (e.g., Verizon,AT&T, T-Mobile) to optimize keepalive or other background traffic intheir mobile networks or may be downloaded by a user (e.g., from an appstore) to reduce bandwidth and power usage.

In one embodiment, the keepalive optimizer 300 can include a keepalivedetector 305, a keepalive blocker 312, a keepalive traffic scheduler314, a background traffic scheduler 316 and/or a keepalive optimizationreporting agent 318. In some embodiments, one or more of thesecomponents can be optional. For example, one embodiment of the keepaliveoptimizer 300 can include the keepalive detector 305, the keepaliveblocker 312 and the keepalive optimization reporting agent 318. FIG. 3Billustrates an example diagram depicting an example of components in thekeepalive blocker 312 of FIG. 3A. FIG. 3C illustrates an example diagramdepicting an example of components in the keepalive traffic scheduler314 of FIG. 3A. FIG. 3D illustrates an example diagram depicting anexample of components in the background traffic scheduler 316 of FIG.3A.

In one embodiment, the keepalive detector 305 detects or identifieskeepalives. The keepalive detector 305 can detect keepalives based onone or more parameters, such as but not limited to: periodicity, sizethresholds, similar/repeating content, and/or based on knowledge of theactual application level protocol. In one embodiment, the keepalivedetector 305 can analyze timeout detection and recovery messages orsocket level network communication log (netlog) data to identifykeepalives from data streams. These and other methods of keepalivedetection are disclosed in related application Ser. No. 61/836039 titled“IDENTIFICATION AND REPORTING OF KEEP ALIVE MESSAGES AND OTHER NON-USERINTERACTIVE TRAFFIC IN A MOBILE NETWORK” (attorney docket no.076443-8173.US02) filed on Jun. 17, 2013, which is expresslyincorporated by reference herein.

Referring to FIG. 3B and as described in reference to FIG. 1A-1, in oneembodiment, the keepalive blocker 312 optimizes keepalives originatingat a mobile device by blocking keepalives based on whether they arenecessary or unnecessary. In one embodiment, the keepalive blocker 312categorizes a keepalive from an application as a safe keepalive or anunsafe keepalive, in which a safe keepalive is a candidate for keepaliveoptimization. The keepalive optimization can include blocking the safekeepalive without causing an impact on the health of a connectionbetween the application and a server to which the keepalive is directed.In one embodiment, the keepalive categorizer 324 b can categorize akeepalive (e.g., detected by the heartbeat manager 267 of FIG. 2A) as asafe keepalive when no other traffic is detected at the same socketwhere the keepalive is detected. In another embodiment, the keepalivecategorizer 324 b can categorize a keepalive as a safe keepalive whentransactions following the keepalive have same or similar byte size. Inyet another embodiment, the keepalive categorizer 324 b can categorize akeepalive as an unsafe keepalive when an indication of user activity(e.g., from the user activity module 215 of FIGS. 2A-2B) ornon-keepalive traffic (e.g., from application traffic categorizer 241d/application behavior detector 236 from FIG. 2A-2B) is detected in thesame TCP stream that includes the keepalive.

Once a keepalive is categorized as safe or unsafe by the keepalivecategorizer 324 b, the keepalive blocker 312 allows the unsafe keepaliveto go to the server (by not blocking) in order to maintain the health ofthe connection between the application and the server or blocks the safekeepalive from going out to the server (via blocking module 326). Byblocking at least some of the safe or unnecessary keepalives, the radiocan be turned on and off less frequently, thereby reducing unnecessarysignaling in the mobile network.

In one embodiment, the keepalive blocker 312 includes a keepaliveprediction engine 320 having a learning module 322, a prediction-basedkeepalive categorizer 324 a and a prediction validation module. Thekeepalive prediction engine 320 (e.g., via the learning module 322)observes keepalive traffic for a period of time to identify one or morefactors for predicting whether a keepalive is a safe or unsafekeepalive. Such factors or predictors can include, but are not limitedto: user, application, hour of the day, day of the week, keepaliveinterval, keepalive byte size, on screen activity or number ofconsecutive safe keepalives. In one embodiment, the learning module 322can be used to generate a rule set for identifying safe keepalives fromunsafe keepalives. Based on one or more of the predictors and/or therule set for keepalive categorization or classification, the keepaliveblocker 312 (e.g., via the prediction-based keepalive categorizer 324 a)categorizes the keepalive as a safe or unsafe keepalive based on the oneor more factors. As before, once the keepalive is categorized orclassified as safe or unsafe, the keepalive blocker 312 (e.g., via theblocking module 326) optimizes the keepalive by blocking the safekeepalive from going out to the server. In one embodiment, the decisionlist learning and blocking algorithm and binary list learning andblocking algorithm described in the present disclosure can be used tocategorize a keepalive as safe or unsafe and selectively block the safekeepalive while allowing the unsafe keepalive to be transmittednormally.

The blocking module 326 can block specific keepalives by blocking theports used by applications that sent the keepalives (e.g., via the portblocker 328) or by blocking the applications themselves (e.g., via theapplication blocker 330) for a duration of time that can be defined bythe PMS or the application. In one embodiment, the unblocking can occurafter the end of the defined duration of time, or after an unblockingevent occurs. The keepalive unblocking module 333 can detect the end ofthe blocking period or other unblocking events such as the screenturning on or change in other external parameters representing start ofactive usage of the application or the device by the user (i.e.,indication of user activity), or deviation from the predicted pattern.Other unblocking events can include, for example, a push message comingin through a parallel push channel, indicating that there is atime-critical message for the application, switching to a network thatis not configured for optimization (e.g., Wi-Fi), or the like.

In one embodiment, the prediction validation module 332 can observetraffic after the blocking of the safe keepalive or after the unblockingevent to validate whether the prediction was successful (i.e., nonecessary keepalive traffic was incorrectly categorized as unnecessaryand blocked) or not (i.e., necessary keepalive traffic missed because itwas incorrectly categorized as unnecessary). The prediction validationmodule 332 can observe the initial data transfer in establishing asocket to determine whether the prediction was successful or not. Forexample, if the prediction validation module 332 detects that a trafficpattern in establishing a socket after the blocking event is differentthan a traffic pattern in establishing a socket without any pendingdata, such difference in traffic patterns can indicate that a datatransfer was prevented because of miscategorization of an unsafekeepalive as safe keepalive. If the prediction failed, the learningmodule 322 is triggered to update its observation and analysis toimprove the prediction capability of the prediction-based keepalivecategorizer 324 a. For example, analysis for determining the keepalivepredictors can be updated, a new rule set can be generated, thresholdsor other parameters can be adjusted, and/or the like.

In one embodiment, instead of blocking the safe keepalive by blockingthe application or the port for a duration of time, a response to thesafe keepalive can be provided by the keepalive synthesizer 334. Thekeepalive synthesizer 334 can synthesize, create or generate a keepalive(or a synthetic keepalive) based on knowledge of the previous keepaliveresponses or acknowledgements, by a piori knowledge of the applicationprotocol, or the like. For example, for a GCM messaging application, thekeepalive synthesizer 334 can provide a synthesized response to akeepalive using the knowledge of the protocol and avoid the risk fromblocking the application or the port which would also prevent theapplication from sending out other data as well as the keepalive.

Referring to FIG. 3C, in one embodiment, the keepalive traffic scheduler314 of the keepalive optimizer 300 includes a keepalive advancer 340and/or a keepalive extender 350. The keepalive advancer 340 can includea keepalive advancing parameter detector 342, a keepalive advancingtrigger module 346, a keepalive executor 344 and a keepalive timermodule 348. As described in reference to FIG. 1A-2, the keepaliveadvancer 340 executes a keepalive (i.e., sends a keepalive)opportunistically, earlier than when an application would normally sendit out. In one embodiment, the keepalive advancing parameter detector342 detects keepalive parameters corresponding to an application. Suchkeepalive parameters can include a keepalive period (or interval betweenkeepalives) and/or a keepalive pull-in period, which is a threshold foradvancement of keepalives defined in order to ensure that keepalives arenot sent more frequently than statistically necessary. The pull-inparameter can be configured by the PMS, by the application or determinedat run time.

In one embodiment, the keepalive advancing trigger module 346 detectsthe radio of the mobile device turning on after a socket for theapplication has been idle for longer than the keepalive pull-in period(e.g., tracked by the keepalive timer module 348) and in response,triggers a new keepalive for execution (e.g., via the keepalive executor344) in advance of the expected schedule. The keepalive advancingtrigger module 346 can trigger a new keepalive by dropping theapplication socket which would cause the application to piggyback on theradio that is already on to establish a new socket. Alternately, insteadof dropping the socket, a new keepalive can be synthesized by thekeepalive synthesizer 345. In one embodiment, the keepalive synthesizer345 can synthesize a keepalive based on an analysis of previouskeepalives at run time or based on knowledge or information obtainedfrom offline analysis of keepalives of an application (or using themethods described with respect to keepalive synthesizer 345). Thekeepalive executor 344 then executes the “advanced” keepalive or the“synthesized” keepalive by transmitting or sending the keepalive to theserver.

In some instances, using synthesized keepalives may cause decoupling ofthe application-side socket (e.g., between application and the localproxy 275) from the network-side socket (e.g., between the local proxy275 and a server such as the host server 125 or the application server)because checksums between the two sockets may be mismatched. In thisinstance, data from the network socket to the application socket may getrejected by the application. The rejection, however, would cause theapplication to re-establish the connection and because the servers aredesigned to retry sending data in the event of failure, there will be nodata loss, with the data reaching the application after a slight delay.

As described in reference to FIG. 1A-3, in one embodiment, the keepaliveextender 350 optimizes keepalive traffic originating at a mobile deviceby identifying keepalive parameters corresponding to an application(e.g., via the keepalive extending parameter detector 352) and utilizingthe keepalive parameters to execute a keepalive after a delay tooptimize the keepalive traffic. In one embodiment, the keepaliveparameters utilized in executing the keepalive after a delay include afirst period or a pattern, a second period and the keepalive period. Inone embodiment, the keepalive extending trigger module 354 detects afirst keepalive after a socket for the application has been idle forlonger than the first period (e.g., as tracked by the keepalive timermodule 358) and delays the keepalive until the radio turns on or thesecond period from the detecting of the first keepalive elapses. Thekeepalive extending trigger module 354 then triggers the keepaliveexecutor 356 to execute the keepalive. Because the keepalive is delayeduntil the radio turns on or until a second period of time from thedetecting of the first keepalive elapses, the keepalive period can beextended up to the time corresponding to the second period.

Referring to FIG. 3D and as described in reference to FIG. 1A-4, in oneembodiment, the background traffic scheduler 316 can optimize backgroundtraffic originating at a mobile device by identifying a backgroundrequest from an application that can be delayed for transmission to awireless network (e.g., via the background request detector 360). Thebackground request detector 360 can characterize a request from anapplication as a background request based on an indication of a lack ofuser interaction with the application or the mobile device or the lackof user interaction with the application/device in combination withother information relating to status of the application or status of themobile device (e.g., status of input/output mechanisms of the mobiledevice). The background traffic scheduler 316 then delays the backgroundrequest for a period of time when a state of the mobile device meets adelay criteria. In one embodiment, the delay criteria is met when thestate of the mobile device is characterized by the mobile device asbeing connected to a mobile network, being in a transparent mode, havinga screen turned off and having a radio turned off. The state of themobile device can be determined and tracked by the device state detector366.

In one embodiment, the background request tolerance detector 362 of thebackground traffic scheduler 316 identifies, detects or determines atolerance for a background request which can be used to determine theperiod of time for which the background request is delayed. A backgroundrequest's tolerance is the shorter of the longest period during which anapplication that generated the background request will not display anerror message to a user of the mobile device and the longest periodbeyond which the application will stop retrying to establish aconnection to the wireless network. The background request tolerancedetector 362 via the background request behavior analyzer 368 canobserve patterns of background requests comprising the backgroundtraffic which can be used to identify a tolerance for a backgroundrequest. For example, the background request behavior analyzer 368 cangradually increase the delay for each type of background request andobserve the application's behavior. Different applications or backgroundrequest types can exhibit different behavior in response to delay inreceiving a response to a background request. One application may timeout and close the socket when a response to a given type of backgroundrequest is not received within a given time (e.g., 15 seconds), whileanother may retry the same background request multiple times beforefinally timing out (e.g., retry the background request every 30 seconds,45 seconds and 1 minute and then time out when no response is receivedafter the fourth attempt). Yet another application may behaveerratically when a response is not received within a given time that canimpact the user experience with the application, while otherapplications may not exhibit any behavior that can disrupt or impact theuser experience. For example, a background request for a “log upload”from one mobile application may tolerate a longer delay because therequest type is not time critical, while a background request fordata/status updates from the same application may have a shortertolerance for delay. The background request behavior analyzer 368 can,based on observation of background traffic and/or application behavior,identify a background request that has no impact on functionality oruser experience on the mobile device. The background request tolerancedetector 362 can then utilize such information to set a predefined ordefault tolerance for such background request with significantly largetolerance.

Because different types of background requests and/or applications canhave different tolerances and can thus be delayed for different periodsof time, the background request delay/undelay module 370 can use orinstantiate different timers (or counters via the delay timer manager364) to delay background requests of different types. For example,background data traffic associated with a log upload can be delayed for5 minutes (i.e., its tolerance detected by the tolerance detector 362)using a timer Timer₁ while a background request for data update (e.g.,score update for ESPN application) can be delayed for 3 minutes (i.e.,its tolerance detected by the tolerance detector 362) using timerTimer₂. Thus, in one embodiment, each background request can be delayedfor the maximum period of time that it has tolerance for. Alternately,in another embodiment, the background request delay/undelay module 370can identify and delay a first background request and a subsequent orsecond background request using the same counter/timer when thesubsequent background request is determined to have no impact onfunctionality or user experience on the mobile device (e.g., viabackground request behavior analyzer 368). For example, a firstbackground request received at time T₀ having a tolerance of 120 secondsand a subsequent background request received at time T₀+40 seconds thatis determined to have no impact on the functionality/user experience canboth be delayed until time T₀+120 seconds using the same timer.

In one embodiment, a TCP session that includes a background request mayalso include a user-interactive request. In this instance, theuser-interactive request can be transmitted to the wireless networkwithout delay, while the background request is delayed by the backgroundrequest delay/undelay module 370 for a period of time allowed by itstolerance. In another embodiment, a TCP session that includes thebackground request may include another background request having alonger or shorter tolerance than that of the background request; andwherein each background request is delayed for the maximum period oftime allowed by the associated tolerance.

The device state detector 366 can detect a change in the state of themobile device. The change in the state (or device state) of the mobiledevice can be triggered by any one of: a screen of the mobile deviceturning on, a radio of the mobile device turning on, the mobile deviceconnecting to Wi-Fi, the mobile device switching to a transparent modeor disabling of the optimization of the background traffic. The delaytimer manager 364 can detect expiration of a delay timer tracking theperiod of time that a background request is being delayed. Thebackground request delay/undelay module 370 can, in response to thechange in the state of the mobile device and/or detection of theexpiration of the period of time, undelay the background request andschedule its transmission to the wireless network.

In one embodiment, a DNS module 249 of the caching policy manager 245depicted in FIG. 2A can cache a DNS request associated with thebackground request to prevent the DNS request from changing the state ofthe mobile device and causing the mobile device to transmit thebackground request to the wireless network before the end of the periodof time.

In one embodiment, the background request can be a repeatable backgroundrequest, and such repeatable background request can also be detected orobserved by the background request detector 360. The background requestdelay/undelay module 370 can then delay the repeatable backgroundrequest for a period of time beyond the tolerance. In one embodiment,the background request tolerance detector 362 can extend the toleranceof the application by modifying system timers (e.g., applicationspecific timers, protocol-specific timers such as HTTP timers, networkstack timers such as TCP stack timers), alarms or other means to causethe application to execute slower, such that the background request isdelayed for a period of time corresponding to the extended tolerance.

In one embodiment, the keepalive optimization reporting agent 318 of thekeepalive optimizer 300 depicted in FIG. 3A logs data relating tooptimizations performed and state of the device and/or application whenthe optimizations were performed. For example, the keepaliveoptimization reporting agent 318 can record each background transactionfor the FACEBOOK application that that occurred and the delay state ofthe mobile device when the transaction occurred. The delay state can,for example, indicate whether the transaction entered a delay mode(i.e., was delayed for a period of time), whether the screen was on,whether the radio was on, whether the undelay trigger was expiration ofthe delay timer, whether the optimization was enabled, and the like.Similarly, other keepalive and background traffic transactions can berecorded in a log and reported periodically to a host server (e.g., hostserver 100 or application servers).

FIG. 4 depicts a block diagram illustrating an example of server-sidecomponents, in certain embodiments of a distributed proxy and cachesystem residing on a host server 400 that manages traffic in a wirelessnetwork (or broadband network) for resource conservation, contentcaching, and/or traffic management. In some embodiments, the server-sideproxy (or proxy server 125) can further categorize mobile traffic and/ordeploy and/or implement policies such as traffic management and deliverypolicies based on device state, application behavior, content priority,user activity, and/or user expectations.

The host server 400 generally includes, for example, a network interface408 and/or one or more repositories 412, 414, and 416. Note that server400 may be any portable/mobile or non-portable device, server, clusterof computers and/or other types of processing units (e.g., any number ofa machine shown in the example of FIG. 1B) able to receive or transmitsignals to satisfy data requests over a network including any wired orwireless networks (e.g., Wi-Fi, cellular, Bluetooth, etc.).

The network interface 408 can include networking module(s) or devices(s)that enable the server 400 to mediate data in a network with an entitythat is external to the host server 400, through any known and/orconvenient communications protocol supported by the host and theexternal entity. Specifically, the network interface 408 allows theserver 400 to communicate with multiple devices including mobile phonedevices 450 and/or one or more application servers/content providers410.

The host server 400 can store information about connections (e.g.,network characteristics, conditions, types of connections, etc.) withdevices in the connection metadata repository 412. Additionally, anyinformation about third-party applications or content providers can alsobe stored in the repository 412. The host server 400 can storeinformation about devices (e.g., hardware capability, properties, devicesettings, device language, network capability, manufacturer, devicemodel, OS, OS version, etc.) in the device information repository 414.Additionally, the host server 400 can store information about networkproviders and the various network service areas in the network serviceprovider repository 416.

The communication enabled by network interface 408 allows forsimultaneous connections (e.g., including cellular connections) withdevices 450 and/or connections (e.g., including wired/wireless, HTTP,Internet connections, LAN, WiFi, etc.) with content servers/providers410 to manage the traffic between devices 450 and content providers 410,for optimizing network resource utilization and/or to conserver power(battery) consumption on the serviced devices 450. The host server 400can communicate with mobile devices 450 serviced by different networkservice providers and/or in the same/different network service areas.The host server 400 can operate and is compatible with devices 450 withvarying types or levels of mobile capabilities, including by way ofexample but not limitation, 1G, 2G, 2G transitional (2.5G, 2.75G), 3G(IMT-2000), 3G transitional (3.5G, 3.75G, 3.9G), 5G (IMT-advanced), etc.

In general, the network interface 408 can include one or more of anetwork adaptor card, a wireless network interface card (e.g., SMSinterface, WiFi interface, interfaces for various generations of mobilecommunication standards including but not limited to 1G, 2G, 3G, 3.5G,5G type networks such as LTE, WiMAX, etc.), Bluetooth, WiFi, or anyother network whether or not connected via a router, an access point, awireless router, a switch, a multilayer switch, a protocol converter, agateway, a bridge, a bridge router, a hub, a digital media receiver,and/or a repeater.

The host server 400 can further include server-side components of thedistributed proxy and cache system which can include a proxy server 125and a server cache 435. In some embodiments, the proxy server 125 caninclude an HTTP access engine 445, a caching policy manager 455, a proxycontroller 465, a traffic shaping engine 475, a new data detector 447and/or a connection manager 495.

The HTTP access engine 445 may further include a heartbeat manager 498;the proxy controller 465 may further include a data invalidator module468; the traffic shaping engine 475 may further include a controlprotocol 476 and a batching module 477. Additional or lesscomponents/modules/engines can be included in the proxy server 125 andeach illustrated component.

In the example of a device (e.g., mobile device 450) making anapplication or content request to an application server or contentprovider 410, the request may be intercepted and routed to the proxyserver 125 which is coupled to the device 450 and the applicationserver/content provider 410. Specifically, the proxy server is able tocommunicate with the local proxy (e.g., proxy 175 of the examples ofFIG. 1C) of the mobile device 450, the local proxy forwards the datarequest to the proxy server 125 in some instances for further processingand, if needed, for transmission to the application server/contentserver 410 for a response to the data request.

In such a configuration, the host 400, or the proxy server 125 in thehost server 400 can utilize intelligent information provided by thelocal proxy in adjusting its communication with the device in such amanner that optimizes use of network and device resources. For example,the proxy server 125 can identify characteristics of user activity onthe device 450 to modify its communication frequency. Thecharacteristics of user activity can be determined by, for example, theactivity/behavior awareness module 466 in the proxy controller 465 viainformation collected by the local proxy on the device 450.

In some embodiments, communication frequency can be controlled by theconnection manager 495 of the proxy server 125, for example, to adjustpush frequency of content or updates to the device 450. For instance,push frequency can be decreased by the connection manager 495 whencharacteristics of the user activity indicate that the user is inactive.In some embodiments, when the characteristics of the user activityindicate that the user is subsequently active after a period ofinactivity, the connection manager 495 can adjust the communicationfrequency with the device 450 to send data that was buffered as a resultof decreased communication frequency to the device 450.

In addition, the proxy server 125 includes priority awareness of variousrequests, transactions, sessions, applications, and/or specific events.Such awareness can be determined by the local proxy on the device 450and provided to the proxy server 125. The priority awareness module 467of the proxy server 125 can generally assess the priority (e.g.,including time-criticality, time-sensitivity, etc.) of various events orapplications; additionally, the priority awareness module 467 can trackpriorities determined by local proxies of devices 450.

In some embodiments, through priority awareness, the connection manager495 can further modify communication frequency (e.g., use or radio ascontrolled by the radio controller 496, Internet/Wi-Fi Controller 497)of the server 400 with the devices 450. For example, the server 400 cannotify the device 450, thus requesting use of the radio if it is notalready in use when data or updates of an importance/priority levelwhich meets a criteria becomes available to be sent.

In some embodiments, the proxy server 125 can detect multipleoccurrences of events (e.g., transactions, content, data received fromserver/provider 410) and allow the events to accumulate for batchtransfer to device 450. Batch transfer can be cumulated and transfer ofevents can be delayed based on priority awareness and/or useractivity/application behavior awareness as tracked by modules 467 and/or466. For example, batch transfer of multiple events (of a lowerpriority) to the device 450 can be initiated by the batching module 477when an event of a higher priority (meeting a threshold or criteria) isdetected at the server 400. In addition, batch transfer from the server400 can be triggered when the server receives data from the device 450,indicating that the device radio is already in use and is thus on. Insome embodiments, the proxy server 125 can order the eachmessages/packets in a batch for transmission based on event/transactionpriority such that higher priority content can be sent first in caseconnection is lost or the battery dies, etc.

In some embodiments, the server 400 caches data (e.g., as managed by thecaching policy manager 455) such that communication frequency over anetwork (e.g., cellular network) with the device 450 can be modified(e.g., decreased). The data can be cached, for example, in the servercache 435 for subsequent retrieval or batch sending to the device 450 topotentially decrease the need to turn on the device 450 radio. Theserver cache 435 can be partially or wholly internal to the host server400, although in the example of FIG. 4 it is shown as being external tothe host 400. In some instances, the server cache 435 may be the same asand/or integrated in part or in whole with another cache managed byanother entity (e.g., the optional caching proxy server 199 shown in theexample of FIG. 1C), such as being managed by an applicationserver/content provider 410, a network service provider, or anotherthird party.

In some embodiments, content caching is performed locally on the device450 with the assistance of host server 400. For example, proxy server125 in the host server 400 can query the application server/provider 410with requests and monitor changes in responses. When changed or newresponses are detected (e.g., by the new data detector 447), the proxyserver 125 can notify the mobile device 450 such that the local proxy onthe device 450 can make the decision to invalidate (e.g., indicated asoutdated) the relevant cache entries stored as any responses in itslocal cache. Alternatively, the data invalidator module 468 canautomatically instruct the local proxy of the device 450 to invalidatecertain cached data, based on received responses from the applicationserver/provider 410. The cached data is marked as invalid, and can getreplaced or deleted when new content is received from the content server410.

Note that data change can be detected by the detector 447 in one or moreways. For example, the server/provider 410 can notify the host server400 upon a change. The change can also be detected at the host server400 in response to a direct poll of the source server/provider 410. Insome instances, the proxy server 125 can, in addition, pre-load thelocal cache on the device 450 with the new/updated data. This can beperformed when the host server 400 detects that the radio on the mobiledevice is already in use, or when the server 400 has additionalcontent/data to be sent to the device 450.

One or more the above mechanisms can be implemented simultaneously oradjusted/configured based on application (e.g., different policies fordifferent servers/providers 410). In some instances, the sourceprovider/server 410 may notify the host 400 for certain types of events(e.g., events meeting a priority threshold level). In addition, theprovider/server 410 may be configured to notify the host 400 at specifictime intervals, regardless of event priority.

In some embodiments, the proxy server 125 of the host 400 canmonitor/track responses received for the data request from the contentsource for changed results prior to returning the result to the mobiledevice; such monitoring may be suitable when data request to the contentsource has yielded same results to be returned to the mobile device,thus preventing network/power consumption from being used when no newchanges are made to a particular requested. The local proxy of thedevice 450 can instruct the proxy server 125 to perform such monitoringor the proxy server 125 can automatically initiate such a process uponreceiving a certain number of the same responses (e.g., or a number ofthe same responses in a period of time) for a particular request.

In some embodiments, the server 400, through the activity/behaviorawareness module 466, is able to identify or detect user activity at adevice that is separate from the mobile device 450. For example, themodule 466 may detect that a user's message inbox (e.g., email or typesof inbox) is being accessed. This can indicate that the user isinteracting with his/her application using a device other than themobile device 450 and may not need frequent updates, if at all.

The server 400, in this instance, can thus decrease the frequency withwhich new or updated content is sent to the mobile device 450, oreliminate all communication for as long as the user is detected to beusing another device for access. Such frequency decrease may beapplication specific (e.g., for the application with which the user isinteracting on another device), or it may be a general frequencydecrease (e.g., since the user is detected to be interacting with oneserver or one application via another device, he/she could also use itto access other services) to the mobile device 450.

In some embodiments, the host server 400 is able to poll content sources410 on behalf of devices 450 to conserve power or battery consumption ondevices 450. For example, certain applications on the mobile device 450can poll its respective server 410 in a predictable recurring fashion.Such recurrence or other types of application behaviors can be trackedby the activity/behavior module 466 in the proxy controller 465. Thehost server 400 can thus poll content sources 410 for applications onthe mobile device 450 that would otherwise be performed by the device450 through a wireless (e.g., including cellular connectivity). The hostserver can poll the sources 410 for new or changed data by way of theHTTP access engine 445 to establish HTTP connection or by way of radiocontroller 496 to connect to the source 410 over the cellular network.When new or changed data is detected, the new data detector 447 cannotify the device 450 that such data is available and/or provide thenew/changed data to the device 450.

In some embodiments, the connection manager 495 determines that themobile device 450 is unavailable (e.g., the radio is turned off) andutilizes SMS to transmit content to the device 450, for instance, viathe SMSC 162 shown in the example of FIG. 1C. SMS is used to transmitinvalidation messages, batches of invalidation messages, or even contentin the case where the content is small enough to fit into just a few(usually one or two) SMS messages. This avoids the need to access theradio channel to send overhead information. The host server 400 can useSMS for certain transactions or responses having a priority level abovea threshold or otherwise meeting a criteria. The server 400 can alsoutilize SMS as an out-of-band trigger to maintain or wake-up an IPconnection as an alternative to maintaining an always-on IP connection.

In some embodiments, the connection manager 495 in the proxy server 125(e.g., the heartbeat manager 498) can generate and/or transmit heartbeatmessages on behalf of connected devices 450 to maintain a backendconnection with a provider 410 for applications running on devices 450.

For example, in the distributed proxy system, local cache on the device450 can prevent any or all heartbeat messages needed to maintain TCP/IPconnections required for applications from being sent over the cellular,or other, network and instead rely on the proxy server 125 on the hostserver 400 to generate and/or send the heartbeat messages to maintain aconnection with the backend (e.g., application server/provider 110 inthe example of FIG. 1B). The proxy server can generate the keepalive(heartbeat) messages independent of the operations of the local proxy onthe mobile device.

The repositories 412, 414, and/or 416 can additionally store software,descriptive data, images, system information, drivers, and/or any otherdata item utilized by other components of the host server 400 and/or anyother servers for operation. The repositories may be managed by adatabase management system (DBMS), for example, which may be but is notlimited to Oracle, DB2, Microsoft Access, Microsoft SQL Server,PostgreSQL, MySQL, FileMaker, etc.

The repositories can be implemented via object-oriented technologyand/or via text files and can be managed by a distributed databasemanagement system, an object-oriented database management system(OODBMS) (e.g., ConceptBase, FastDB Main Memory Database ManagementSystem, JDOInstruments, ObjectDB, etc.), an object-relational databasemanagement system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS,etc.), a file system, and/or any other convenient or known databasemanagement package.

FIGS. 5-6 illustrate example logic flow diagrams for optimizingkeepalives by categorizing a keepalive as safe or unsafe andtransmitting an unsafe keepalive from a mobile device to the network,while blocking a safe keepalive from going out to the network.

Referring to the method 500 described in FIG. 5, the keepalive optimizer300 detects a keepalive at block 505. One or more determinations aremade at decision blocks 510, 515 and 520 to categorize the keepalive assafe or unsafe. For example, at decision block 510, if the keepaliveoptimizer detects no other traffic at the same socket where thekeepalive is detected, the keepalive is categorized as safe at block525, otherwise the keepalive is categorized as unsafe at block 535.Similarly, at decision block 515, if a transaction subsequent to thekeepalive transaction has the same or similar byte size, then thekeepalive optimizer 300 can categorize the keepalive as safe at block525, otherwise the keepalive is categorized as unsafe at block 535. Byway of another example, if the keepalive optimizer 300 detects useractivity or non-keepalive traffic in the TCP stream before the nextkeepalive, the keepalive is categorized as unsafe at block 535, becausethe user activity or non-keepalive traffic is an indication thateliminating the keepalive may prevent the transmission ofuser-interactive traffic to the network. When the keepalive iscategorized as safe at block 525, the keepalive optimizer 300 at block530 blocks the safe keepalive by blocking the application from which thekeepalive originated or the application port for a period of time. Whenthe keepalive is categorized as unsafe at block 535, the keepaliveoptimizer 300 can send the unsafe keepalive to the network at block 540.

In one embodiment, after detecting the keepalive at block 505, theprocess flow continues to method 600 at block 615 in FIG. 6 where thekeepalive optimizer 300 predicts whether the keepalive is safe or unsafebased on keepalive predictors or factors that can be used to predictwhether the keepalive is safe or unsafe. In one embodiment, thekeepalive optimizer 300 observes keepalive traffic for a period of timeat block 605 and determines keepalive predictors and/or rules forpredicting or classifying a keepalive as safe or unsafe at block 610.These predictors can include, for example, hours of the day, days of theweek, keepalive interval, keepalive byte size, on-screen activity, timebetween last on-screen activity and current keepalive, and/or number ofconsecutive safe keepalives. At block 620, the keepalive optimizer 300can block the unsafe keepalive by blocking the application port or theapplication itself for a duration of time.

In one embodiment, after the blocking event, the keepalive optimizer 300can observe the traffic to validate the prediction (i.e., whether theprediction was successful or not) at block 625. For example, thekeepalive optimizer 300 can observe that a traffic pattern afterestablishing a socket after a blocking event is different from thetraffic pattern after establishing a socket with no pending data totransfer, indicating that an unsafe keepalive was missed which preventedthe pending data from being transferred to the network. At block 630, ifthe prediction was successful, the prediction model is not modified.However, if the prediction was not successful, the prediction model isupdated to update the determination of keepalive predictors and/or rulesfor predicting a keepalive as safe or unsafe at block 635.

FIG. 7 illustrates an example logic flow diagram for optimizingkeepalive traffic by advancing a keepalive from its expected schedule.As illustrated in the example method 700, the keepalive optimizer 300determines, identifies or retrieves a keepalive pull-in parameter for anapplication at block 705 based on which a keepalive is pulled in oradvanced from its expected schedule. At block 710, the keepaliveoptimizer 300 detects or determines that the application socket is idlefor a time longer than the pull-in period. After the application sockethas been idle for a time longer than the pull-in period, the keepaliveoptimizer 300 detects the radio turn on at block 715. In response, thekeepalive optimizer 300 triggers a new keepalive at block 720.Triggering the new keepalive can include synthesizing a new keepalive orterminating the connection. Terminating the connection when the radio ison allows the application to send a new keepalive piggybacking on theradio that is already on. At block 725, the keepalive optimizer 300executes the keepalive by sending the keepalive to the network inadvance of the expected schedule. In some embodiments, the keepalive canbe executed in advance, i.e., it can occur after identifying a firstkeepalive period or even before. For example, when the network closesthe socket after 2 minutes of inactivity while an application performskeepalive every 3 minutes, the application socket would keep closing thesocket causing user experience issues with the application. In thisinstance, by triggering a new keepalive before the network closes thesocket (e.g., after 110 seconds), the keepalive optimizer 300 can keepthe long-lived connection alive and improve the user experience.

FIG. 8 illustrates an example logic flow diagram for optimizingkeepalive traffic by delaying a keepalive beyond the keepalive period.In the example method 800, the keepalive optimizer 300 identifieskeepalive parameters for an application at block 805. Such parameterscan include a first period (X₁) or pattern, a second period (X₂) and/ora keepalive interval. At block 810, the keepalive optimizer 300determines or detects that a socket for the application has been idlefor a time longer than the first period. The keepalive optimizer 300intercepts any keepalive transactions detected after the end of thefirst period at block 815. When the keepalive optimizer 300 detects themobile device radio turn on at block 820 after the first period butbefore the second period from the detection of a keepalive transactionelapses, the keepalive optimizer 300 identifies and sends the latestkeepalive transaction to the network at block 825. Alternately, if thesecond period from the detection of a keepalive transaction elapses atblock 835 before the radio turns on, the keepalive optimizer 300 canidentify and send the latest keepalive transaction to the network. Thus,by using the method 700, a keepalive interval of T₀ can be extended byup to X₂ to T₀+X₂.

FIGS. 9-11 illustrate example logic flow diagrams for optimizingbackground traffic by delaying repeatable background requests.

The example method 900 of FIG. 9 shows the determination of applicationtolerance for a background request. At block 905, the keepaliveoptimizer 300 observes patterns of the background request. In oneembodiment, the observation is related to the behavior of theapplication(s) from where the background request originates. From theobservation, the keepalive optimizer 300 determines the longest periodduring which an application can wait for a response to a backgroundrequest without displaying an error message, impacting the functionalityof the application or the user experience at block 910. At block 915,the keepalive optimizer 300 determines the longest period beyond whichthe application will stop retrying to establish a connection to thewireless network. At block 920, the keepalive optimizer 300 determinesor identifies the shorter of the two periods from blocks 910 and 915 asthe tolerance for the background request at block 920. For example, thekeepalive optimizer 300 may observe that the WEATHER mobile applicationwaits for a period of 150 s to receive a response to the “weatherupdate” background request from the WEATHER application server beforedisplaying an error message to the user and that the application retriesthe request rapidly in intervals of 10 s, 60 s and 120 s before stoppingthe retry attempts. In this example, the background request has atolerance of 120 s.

Referring to the example method 1000 in FIG. 10, the keepalive optimizer300 collects data characterizing the device state of the mobile deviceto determine if the device state meets the delay criteria. In oneembodiment, the keepalive optimizer 300 determines that the device statemeets the delay criteria at block 1035 if the mobile device is on themobile network (at decision block 1010), the mobile device is not intransparent mode (at decision block 1015), the mobile device has screenoff (at decision block 1020), the mobile device has radio off (atdecision block 1025) and the optimization is enabled by the PMS (atdecision block 1030). Alternately, if the mobile device is not on themobile network (at decision block 1010), the mobile device is intransparent mode (at decision block 1015), the mobile device has screenon (at decision block 1020), the mobile device has radio on (at decisionblock 1025) or the optimization is disabled by the PMS (at decisionblock 1030), at block 1040, the keepalive optimizer 300 determines thatthe device state does not meet the delay criteria.

Referring to the example method 1100 of FIG. 11, the keepalive optimizer300 identifies a background request at block 1105 determines whether thedevice state meets the delay criteria at decision block 1106, If thedevice state meets the delay criteria, the keepalive optimizer 300delays the background request for a period of time that the backgroundrequest has tolerance for (e.g., based on information item B from FIG.9) at block 1110. Conversely, if the device state fails to meet thedelay criteria, the background request is not delayed, and is insteadallowed to go to the network at block 1107. At block 1115, the keepaliveoptimizer 300 detects an undelay trigger. The undelay trigger can be achange in the device state of the mobile device (or the device statemeeting the undelay criteria) or expiration of a period of time. Forexample, if the mobile device switches from mobile network to Wi-Fi, themobile device switches to transparent mode, the mobile device screenturns on, the mobile device radio turns on, the optimization is disabledor turned off or a delay timer tracking the period of time ends, theundelay criteria is met and the background request can be allowed to goto the network. The keepalive optimizer 300 then transmits thebackground request to the wireless network at block 1125.

FIG. 12 shows a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

In the example of FIG. 12, the computer system 1200 includes aprocessor, memory, non-volatile memory, and an interface device. Variouscommon components (e.g., cache memory) are omitted for illustrativesimplicity. The computer system 1200 is intended to illustrate ahardware device on which any of the components depicted in the exampleof FIGS. 2A-2C (and any other components described in thisspecification) can be implemented. The computer system 1200 can be ofany applicable known or convenient type. The components of the computersystem 1200 can be coupled together via a bus or through some otherknown or convenient device.

The processor may be, for example, a conventional microprocessor such asan Intel Pentium microprocessor or Motorola power PC microprocessor. Oneof skill in the relevant art will recognize that the terms“machine-readable (storage) medium” or “computer-readable (storage)medium” include any type of device that is accessible by the processor.

The memory is coupled to the processor by, for example, a bus. Thememory can include, by way of example but not limitation, random accessmemory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). Thememory can be local, remote, or distributed.

The bus also couples the processor to the non-volatile memory and driveunit. The non-volatile memory is often a magnetic floppy or hard disk, amagnetic-optical disk, an optical disk, a read-only memory (ROM), suchas a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or anotherform of storage for large amounts of data. Some of this data is oftenwritten, by a direct memory access process, into memory during executionof software in the computer 1200. The non-volatile storage can be local,remote, or distributed. The non-volatile memory is optional becausesystems can be created with all applicable data available in memory. Atypical computer system will usually include at least a processor,memory, and a device (e.g., a bus) coupling the memory to the processor.

Software is typically stored in the non-volatile memory and/or the driveunit. Indeed, for large programs, it may not even be possible to storethe entire program in the memory. Nevertheless, it should be understoodthat for software to run, if necessary, it is moved to a computerreadable location appropriate for processing, and for illustrativepurposes, that location is referred to as the memory in this paper. Evenwhen software is moved to the memory for execution, the processor willtypically make use of hardware registers to store values associated withthe software, and local cache that, ideally, serves to speed upexecution. As used herein, a software program is assumed to be stored atany known or convenient location (from non-volatile storage to hardwareregisters) when the software program is referred to as “implemented in acomputer-readable medium.” A processor is considered to be “configuredto execute a program” when at least one value associated with theprogram is stored in a register readable by the processor.

The bus also couples the processor to the network interface device. Theinterface can include one or more of a modem or network interface. Itwill be appreciated that a modem or network interface can be consideredto be part of the computer system. The interface can include an analogmodem, ISDN modem, cable modem, token ring interface, satellitetransmission interface (e.g. “direct PC”), or other interfaces forcoupling a computer system to other computer systems. The interface caninclude one or more input and/or output devices. The I/O devices caninclude, by way of example but not limitation, a keyboard, a mouse orother pointing device, disk drives, printers, a scanner, and other inputand/or output devices, including a display device. The display devicecan include, by way of example but not limitation, a cathode ray tube(CRT), liquid crystal display (LCD), or some other applicable known orconvenient display device. For simplicity, it is assumed thatcontrollers of any devices not depicted in the example of FIG. 12 residein the interface.

In operation, the computer system 1200 can be controlled by operatingsystem software that includes a file management system, such as a diskoperating system. One example of operating system software withassociated file management system software is the family of operatingsystems known as Windows® from Microsoft Corporation of Redmond, Wash.,and their associated file management systems. Another example ofoperating system software with its associated file management systemsoftware is the Linux operating system and its associated filemanagement system. The file management system is typically stored in thenon-volatile memory and/or drive unit and causes the processor toexecute the various acts required by the operating system to input andoutput data and to store data in the memory, including storing files onthe non-volatile memory and/or drive unit.

Some portions of the detailed description may be presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the methods of some embodiments. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, the techniques are not described withreference to any particular programming language, and variousembodiments may thus be implemented using a variety of programminglanguages.

In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a laptop computer, a set-top box (STB), apersonal digital assistant (PDA), a cellular telephone, an iPhone, aBlackberry, a processor, a telephone, a web appliance, a network router,switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine.

While the machine-readable medium or machine-readable storage medium isshown in an exemplary embodiment to be a single medium, the term“machine-readable medium” and “machine-readable storage medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” and “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include but are not limitedto recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is notintended to be exhaustive or to limit the teachings to the precise formdisclosed above. While specific embodiments of, and examples for, thedisclosure are described above for illustrative purposes, variousequivalent modifications are possible within the scope of thedisclosure, as those skilled in the relevant art will recognize. Forexample, while processes or blocks are presented in a given order,alternative embodiments may perform routines having steps, or employsystems having blocks, in a different order, and some processes orblocks may be deleted, moved, added, subdivided, combined, and/ormodified to provide alternative or subcombinations. Each of theseprocesses or blocks may be implemented in a variety of different ways.Also, while processes or blocks are at times shown as being performed inseries, these processes or blocks may instead be performed in parallel,or may be performed at different times. Further any specific numbersnoted herein are only examples: alternative implementations may employdiffering values or ranges.

The teachings of the disclosure provided herein can be applied to othersystems, not necessarily the system described above. The elements andacts of the various embodiments described above can be combined toprovide further embodiments.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the disclosure can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further embodiments of thedisclosure.

These and other changes can be made to the disclosure in light of theabove Detailed Description. While the above description describescertain embodiments of the disclosure, and describes the best modecontemplated, no matter how detailed the above appears in text, theteachings can be practiced in many ways. Details of the system may varyconsiderably in its implementation details, while still beingencompassed by the subject matter disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the disclosure should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the disclosure with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the disclosure to the specific embodimentsdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe disclosure encompasses not only the disclosed embodiments, but alsoall equivalent ways of practicing or implementing the disclosure underthe claims.

While certain aspects of the disclosure are presented below in certainclaim forms, the inventors contemplate the various aspects of thedisclosure in any number of claim forms. For example, while only oneaspect of the disclosure is recited as a means-plus-function claim under35 U.S.C. §112, ¶6, other aspects may likewise be embodied as ameans-plus-function claim, or in other forms, such as being embodied ina computer-readable medium. (Any claims intended to be treated under 35U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, theapplicant reserves the right to add additional claims after filing theapplication to pursue such additional claim forms for other aspects ofthe disclosure.

1. A method of optimizing network transaction traffic originating at amobile device, comprising: identifying network transaction parameterscorresponding to an application; utilizing the network transactionparameters to execute a network transaction in advance of an expectedschedule or after a delay to optimize the network transaction traffic;wherein execution of the network transaction in advance of the expectedschedule is triggered in response to detecting a radio state of themobile device transition from an idle state to a connected state after asocket for the application has been idle for longer than the pull inperiod.
 2. The method of claim 1, wherein the network transactionparameters utilized in executing the network transaction in advance ofthe expected schedule includes a pull in period and a networktransaction period.
 3. (canceled)
 4. The method of claim 3, wherein thenetwork transaction that is executed in advance of the expected scheduleis triggered by terminating a connection for the application.
 5. Themethod of claim 1, wherein the network transaction parameters utilizedin executing the network transaction after a delay includes a firstperiod or a pattern, a second period and the network transaction period.6. The method of claim 5, further comprising: detecting the networktransaction after a socket for the application has been idle for longerthan the first period, wherein execution of the network transaction istriggered when either one of a radio state of the mobile devicetransitions from an idle state to a connected state or a timecorresponding to the second period from the detection of the networktransaction elapses.
 7. The method of claim 1, wherein a local proxy onthe mobile device optimizes the network transaction traffic associatedwith multiple applications by executing network transactions from eachof the multiple applications in advance of an expected schedule or aftera delay.
 8. The method of claim 1, wherein the application optimizes thenetwork transaction traffic by executing a network transaction inadvance of an expected schedule or after a delay.
 9. A mobile deviceoptimizing network transaction traffic, comprising: a radio and aprocessor; the processor configured to identify network transactionparameters corresponding to an application; the processor furtherconfigured to utilize the network transaction parameters to execute anetwork transaction in advance of an expected schedule or after a delayto optimize the network transaction traffic; wherein execution of thenetwork transaction in advance of the expected schedule is triggered inresponse to detecting a radio state of the mobile device transition froman idle state to a connected state after a socket for the applicationhas been idle for longer than the pull in period.
 10. The mobile deviceof claim 9, wherein the network transaction parameters utilized inexecuting the network transaction in advance of the expected scheduleincludes a pull in period and the network transaction period. 11.(canceled)
 12. The mobile device of claim 11, wherein the networktransaction that is executed in advance of the expected schedule istriggered by terminating a connection for the application.
 13. Themobile device of claim 9, wherein the network transaction parametersutilized in executing the network transaction after a delay includes afirst period or a pattern, a second period and the network transactionperiod.
 14. The mobile device of claim 13, wherein the processor isfurther configured to: detect the network transaction after a socket forthe application has been idle for longer than the first period, whereinexecution of the network transaction is triggered when either one of theradio state of the mobile device transitions from an idle state to aconnected state or a time corresponding to the second period from thedetection of the network transaction elapses.
 15. The mobile device ofclaim 9, further comprising a local proxy that optimizes the networktransaction traffic associated with multiple applications by executingnetwork transactions from each of the multiple applications in advanceof an expected schedule or after a delay.
 16. The mobile device of claim9, wherein the application optimizes the network transaction traffic byexecuting a network transaction in advance of an expected schedule orafter a delay.
 17. A system for optimizing network transaction trafficoriginating at a mobile device, comprising: means for identifyingnetwork transaction parameters corresponding to an application; andmeans for utilizing the network transaction parameters to execute anetwork transaction in advance of an expected schedule or after a delayto optimize the network transaction traffic; wherein execution of thenetwork transaction in advance of the expected schedule is triggered inresponse to detecting a radio state of the mobile device transition froman idle state to a connected state after a socket for the applicationhas been idle for longer than the pull in period.
 18. The system ofclaim 17, wherein the network transaction parameters utilized inexecuting the network transaction in advance of the expected scheduleincludes a pull in period and the network transaction period. 19.(canceled)
 20. The system of claim 19, wherein the network transactionthat is executed in advance of the expected schedule is triggered byterminating a connection for the application or generation of asynthetic network transaction.
 21. The system of claim 18, wherein thenetwork transaction parameters utilized in executing the networktransaction after a delay includes a first period or a pattern, a secondperiod and the network transaction period.
 22. The system of claim 21,further comprising: means for detecting the network transaction after asocket for the application has been idle for longer than the firstperiod, wherein execution of the network transaction is triggered wheneither one of a radio state of the mobile device transitions from anidle state to a connected state or a time corresponding to the secondperiod from the detection of the network transaction elapses.
 23. Thesystem of claim 18, further comprising a means for optimizing thenetwork transaction traffic associated with multiple applications byexecuting network transactions from each of the multiple applications inadvance of an expected schedule or after a delay.
 24. Acomputer-readable storage medium storing instructions that when executedby a processor, causes the processor to: identify network transactionparameters corresponding to an application; utilize the networktransaction parameters to execute a network transaction in advance of anexpected schedule or after a delay to optimize the network transactiontraffic; wherein execution of the network transaction in advance of theexpected schedule is triggered in response to detecting a radio state ofthe mobile device transition from an idle state to a connected stateafter a socket for the application has been idle for longer than thepull in period.